wrkr report

Synopsis

wrkr report [--json] [--explain] [--md] [--md-path <path>] [--pdf] [--pdf-path <path>] [--template exec|operator|audit|public] [--share-profile internal|public] [--baseline <path>] [--previous-state <path>] [--top <n>] [--state <path>]

Flags

• --json
• --explain
• --md
• --md-path
• --pdf
• --pdf-path
• --template
• --share-profile
• --baseline
• --previous-state
• --top
• --state

Example

wrkr report --md --md-path ./.tmp/wrkr-summary.md --template operator --share-profile internal --json
wrkr report --pdf --pdf-path ./.tmp/wrkr-summary.pdf --template exec --json
wrkr report --md --md-path ./.tmp/wrkr-summary-public.md --template public --share-profile public --json

Expected JSON keys: status, generated_at, top_findings, total_tools, tool_type_breakdown, compliance_gap_count, summary, md_path, pdf_path.

Coverage semantics

Report compliance/posture values are derived from evidence present in the current scan state.

• Low compliance/coverage in report output indicates control evidence gaps in the scanned snapshot.
• Low compliance/coverage does not imply Wrkr lacks framework support.
• Use report findings as remediation priorities, then rerun deterministic scan/evidence/report commands to confirm improvement.