Repository navigation
v0.195.22
·
175 commits
to main
since this release
Measured, 0.195.21: TIMINGS preflight=3s push=5s pr=4s checks=393s merge=5s verify=6s tag=2s release=223s npm=145s total=786s release-clock=236s, shipped in 14 min 56 s on the third attempt (the first stopped at verify on the new expected-jobs rule because the check-runs query had never been paginated; the second stopped at the warm gate because the CodeQL summary check is not a workflow job). The npm check was re-run once with --resume.
The safety and semantics items of the GA plan that are code (GA-07.4, GA-07.5, GA-11.7, its day 5 and day 6, and the two contract failures its review found), built on the 0.195.21 ledger.
- Detector-spec synthesis goes through the shared bounded model call.
scripts/synthesize-detector.mjsposted its prompt with a barefetch: no egress policy, no redaction, no deadline, a regular-expression JSON extractor that could not parse the nested array it required, and an output path written anywhere. It is now a thin front overscanner/src/discovery/detector-spec-synthesis.js: thedetector-spec-synthesisassurance feature (off by default), the egress policy evaluated BEFORE any sample file is read (a denied call reads nothing), bounded reads, a CSPRNG nonce,guardedModelCall(redaction, request cap, deadline with bounded retries, audit entry, output cap), the string-aware JSON parser the validator uses, and a closed-world validation of the proposal (identifiers only, so no field can carry a pattern; unknown fields, a wrong nonce and a bad argument index are refused with reasons, never with the raw reply). A proposal is written only inside the working directory, never underscanner/src, never over a file without--force; nothing installs it. Exit codes 0, 2, 3, 4. Eleven pins with an injected transport, and themodel-egress-policycontract test now covers this path. - The autopilot's fix proposals too.
scripts/autopilot.mjswas the second model path the 0.195.21 egress check found: its whole-file fix prompt now goes through the egress policy (a denial leaves the finding NEEDS_REVIEW), the redactor and the audit log. Themodel-egress-policy:EGRESS-ALL-PATHSledger record moves fromfailedtopassed. - One assurance decision on every surface.
posture/assurance/decision.js:deployable,needs_review,not_deployable, orunknownwhen no scan health was recorded. The CLI ship verdict, the Slack, Discord and Teams digests and the pull-request comment all derive their wording from it;digestreads the scan health the last scan recorded. A findings file with no scan health now reads "cannot confirm", never "safe to deploy", and a scan object without scan health in the tests was re-pinned to that. The default wording of the three existing states is unchanged (the bounded wording stays theportfolio-assuranceopt-in). - Unknown feed freshness is a condition.
freshness.<feed>.staleis tri-state and documented so;nullfor a feed the scan consulted (consulteditems for the KEV catalog,cvesCheckedfor EPSS) because it was unavailable, never loaded or cached without a timestamp is a condition like staleness, the result ispartialand strict mode fails closed on it. A feed the scan had nothing to look up in is not a condition, and neither isoffline-skipped, the operator's own declared configuration. The catalog metadata is reset per scan so one scan cannot inherit another's. The test that asserted a boolean, and the offline clean-scan pin, now assert the tri-state and the feed-only conditions. - A suppression pragma now reaches privacy-flow findings. The self-scan of the new synthesis module showed that
agentic-security-ignoreon a credential-to-HTTP line was inert: the privacy flows (dataflow/privacy-taint.js) are appended after both pragma passes, against the documented rule that a stage appending findings runs the filter after itself. A third pass runs after the privacy stage; pinned both ways with a deep-mode fixture, and the suppression is logged like every other. - The
proof doctorexit code is documented. 0 when an execution environment is usable, 1 when none is (the report is still printed),--jsonalways 0. The contract test that demanded 0 on every host, and so failed on one without a confinement backend, now pins the documented contract; the CLI's behaviour is unchanged.