Repository navigation
CodeWitness 1.0.17
CodeWitness 1.0.17 corrects the self-check's own README, which still described the check as it was
before 1.0.2 — a rule it could not execute, a run of 1,671 tests and ten findings.
What changed
selfcheck/README.mdno longer claims that the exit-code rule cannot be executed. Its table said
CWR-007had no scenario, "so the honest verdict isUNVERIFIED", and the paragraph beneath
explained why leaving one ground rule unexecuted was deliberate.mode: processmade that rule
executable in 1.0.2, and the self-check has reported itVERIFIEDby running the built jar ever
since. The row now says what the scenario does, and the paragraph records the history without
claiming the present: the behaviour that an unexecutable claim staysUNVERIFIEDis still exercised,
bySC-CWR-002, which asserts that verdict againstVerdictCalculator.- The quoted result is replaced with a current one. The block cited run
CW-2026-10-25-2415C:
1,671 tests,PARTIALLY_VERIFIED, six verified and one unverified. It now quotes run
CW-2026-10-26-XRNH0— 1,759 tests all passing, coverage line 71.2 % (25562/35919) and branch 59.4 %
(12413/20890), 30 dependencies with no advisory, all seven requirementsVERIFIED, exit0— and
says which fixes were in place. - "Known false positives" now describes the report that exists. It said "the static-analysis
section reports 10 findings (1 high, 9 medium)", which stopped being true in 1.0.13. It now states
that there are no unsuppressed findings, names the five suppressed ones by rule, file and reason,
and records that the phase line discloses the suppression (2 medium (2 suppressed by configuration))
so a reader can reconcile the two counts.
None of this is a behaviour change. It is the same failure mode this project has fixed before, in the
landing page in 1.0.12: documentation outliving the feature it describes. The correction matters more
here than elsewhere, because this is the document that tells a reader what the self-check actually
proves — a reader who believed the old text would conclude that the project's strongest claim still
leaves one ground rule unexecuted, and that the report carries ten findings it has to triage.
What this does not fix
- The five suppressed findings are still suppressed, for the reasons the section now states. They are
judgements about this project, not defects, and suppression is disclosed in the run. - No code, test, report or configuration changed, so nothing about what CodeWitness verifies moved.
Verified for this release
- Documentation only: apart from the version constant, no source file changed, and the full reactor suite
is unchanged at 1,759 tests, 0 failures. - Every number written into
selfcheck/README.mdwas read from the report of run
CW-2026-10-26-XRNH0— the 1.0.16 self-check, which is also the run that verified the two fixes in
1.0.15 and 1.0.16 — rather than recalled.
Compatibility
- No interface change of any kind: CLI, exit codes, report keys, SARIF and
codewitness.yamlare
untouched.