Skip to content
Sarj Repo Standards
core/baseline/stale-entry

Remove resolved findings from the baseline

The ratchet baseline contains only fingerprints still emitted as active errors.

error

Examples

FlaggedFails
{"schema_version":1,"repository_id":"example-repository","policy":"example","policy_version":1,"scope_digest":"scope","fingerprints":["ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff"]}
PassesClean
{"schema_version":1,"repository_id":"example-repository","policy":"example","policy_version":1,"scope_digest":"scope","fingerprints":[]}

Why it matters

Resolved debt remains recorded, so the baseline no longer shows the repository's actual remaining error budget or locks in cleanup.

How detection works

After repository, policy, and scope validation, reports each baseline fingerprint absent from the current active-error fingerprint set.

What is inspected

  • The reviewed baseline and fingerprints of current active error findings.

Limits

  • Removing fingerprints that still match active error findings.

How to fix it

Delete the resolved fingerprint from the reviewed baseline.

  1. Remove the exact resolved fingerprint from .repo-lint/baseline.json.

Verify

  • Run repo-lint check --mode ratchet again.