Snapshots and Assessments turn current repository evidence into a frozen, professionally structured report. Every section explains what it measures, how to read it, and what the evidence cannot establish.
These pages show the current report layout. The public Snapshot is available now; the Assessment sample is withheld until its contributor ranking is regenerated with granular per-commit attribution.
Both reports are current at an identified commit. The Assessment adds the contributor, continuity, structural-risk, and diligence detail needed for higher-stakes review.
Use the Snapshot when the decision needs the full current valuation basis, codebase composition, delivery accounting, structural posture, accepted-value activity, and evidence coverage in one frozen record.
Use the Assessment for acquisition, investment, vendor-risk, financing, or executive review that also needs contributor concentration, code durability, technical-debt signals, architecture, verification, migrations, hygiene, and an overall scorecard.
The Snapshot is not a collection of headline cards. It reconciles the estimate and the repository evidence that produced it.
Reconciles RepoWorth to the visible source corpus, development difficulty, expert delivery effort, compute basis, and bounded delivery-risk reserve.
Identifies the repository, default branch, exact cutoff commit, scan date, measured files, source tokens, tests, documentation, and coverage.
Reports accepted source added, deleted, rewritten, removed, gross movement, and net footprint without treating raw volume as productivity.
Groups 52 weeks of accepted change value into a time series so the reader can see delivery continuity and concentration in time.
Summarizes complexity, maintainability, verification surface, architecture breadth, dependencies, and refactor pressure at the cutoff.
Shows commit coverage, patch coverage, exclusions, estimates, scanner identity, and the boundaries on every reported conclusion.
Use this table to confirm exactly where the two products differ. Feature-level views such as personal streaks and day-to-day Contributor Value remain on their dedicated product pages.
Each major section states its purpose, measurement basis, current reading, and decision boundary so a board, evaluator, or technical reviewer does not have to infer what a metric means.
Use these answers to confirm the package, cutoff, access boundary, and delivery format.
A Snapshot reconciles the complete current RepoWorth, repository composition, Shipped Tokens, accepted-value activity, technical posture, and evidence coverage. An Assessment adds contributor, concentration, durability, structural-risk, diligence, continuity, and scorecard sections.
Each report is frozen at an identified repository commit and scan cutoff. Where the package includes a 52-week chart or ledger analysis, that historical activity is measured through the stated cutoff rather than presented as a prior report comparison.
No. Reports contain derived measurements, evidence summaries, repository identifiers, coverage, and disclosed boundaries. They do not include source code, credentials, raw diffs, or private filenames.
Yes. Authorized evaluators and organization administrators can open the read-only web report and its finished PDF. Signed PDF links expire after seven days and can be regenerated while the account remains authorized.
The authorized organization administrator controls the repository connection and report approval. Evaluators receive only the approved read-only report and never receive repository credentials or source access.