Skip to content

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

2.4 KB
Raw Blame

Evidence Reports

repowise report writes documents a team hands to someone else: an auditor, an acquirer, a board or a migration committee. Each is built from the local index, and JSON is the canonical form, with Markdown, CSV and a self-contained HTML file that opens offline.

Report What it holds Typical reader
report assessment Component posture, hotspots, bus factor, dead code by tier, test reach, contracts, governing decisions, provenance coverage and what moved in the last quarter Acquirer, board, platform lead, migration committee
report changes Every change merged in a period: components and owning teams, review record, reaching tests, policy verdict, provenance and later outcome, with a period summary Auditor reviewing change management (SOC 2 CC8.1, ISO 27001 A.8.32, PCI DSS 6.5)
report inventory Components with owner teams, languages, entry points and the packages they import Software inventory review (PCI DSS 6.3.2)
report estate A workspace's repos and services, the system map and architecture with the evidence behind them, contracts and the calls that reached no provider, health and churn per repo, the riskiest seams and where to start Platform lead, acquirer, team taking over an estate
repowise report assessment --format html --out assessment.html
repowise report changes --since 2026-07-01 --format markdown --out q3-changes.md
repowise report inventory --format csv --out inventory.csv

In a workspace, report assessment and report inventory cover every repository. report estate covers the workspace as one system, from what repowise update --workspace stored.

How to read them

Every item says how it is known: measured, inferred, declared or unresolved. Missing evidence is reported as unresolved, never as a low score or a pass. Assessment items keep the OpenSSF Scorecard check shape, so existing tooling can read them. The change report ends with a method appendix that states what git alone cannot attest, such as a review that left no trace in the history.

The reports describe code and components. Owners and reviewers are counted, never ranked or named, and local paths are removed. They are evidence for a review, not a certification.

Sections and renderers are plugin seams, so an organisation can add its own section or output format. Every section and option: the CLI reference.