agents: the hosted witness for agent ledgers (sandbox on testnet 28001), its probe and negative control; crypto-inventory 0.4.1 resolves a minimum TLS version given through a constant or a ternary; proof-kinds and conformance gain the agent-witness-checkpoint kind; the reproduction scripts of the Shield recipes no longer carry a workstation path

This commit is contained in:
Aere Network committed 2026-10-20 01:04:12 +03:00
1 parent 0c8f1de3fd
commit a654c3d522
27 files changed
+4737 -43

No files matched your search

+8 -1
View File
@@ -68,6 +68,13 @@ tool does not guess. At most 64 distinct variables are resolved per file; past t
file are reported as `unknown`, and the file is counted (`files-over-resolution-limit` in the CBOM, a
line in the text summary).
The TLS protocol version of a Node.js option (`minVersion`, `maxVersion`, `tls.DEFAULT_MIN_VERSION`, `tls.DEFAULT_MAX_VERSION`) is
resolved the same way since 0.4.1 (2026-10-19): a constant holding a version string is followed, and a constant assigned a
conditional between two version strings (`const min = strict ? 'TLSv1.3' : 'TLSv1.2'`) is reported with the WEAKER of the two,
since that is the version the code can end up allowing; `resolvedFrom` names the line and says it was a conditional. Any other
expression gives an `unknown` finding. Before 0.4.1 a version given through a variable produced no TLS finding at all, not even an
`unknown` one; it was found on our own TLS gateway, whose upstream minimum had moved into such a constant.
## Cost on hostile input
The scanner reads repositories it did not write, so its cost is kept linear in the size of each file,
@@ -215,7 +222,7 @@ console.log(renderSummary(result));
```
node test/proba.mjs # 68 probes: fixtures per language with the exact expected findings
node test/control-negativ.mjs # breaks the scanner in a copy, one rule at a time (35 mutations), and
node test/control-negativ.mjs # breaks the scanner in a copy, one rule at a time (38 mutations), and
# requires the matching probe to fail while the rest of the suite still runs
node test/proba-timp.mjs # 13 hostile inputs, each at two sizes: the cost must grow linearly
node test/control-negativ-timp.mjs # puts each quadratic form back (and one Swift comment rescan) and requires the cost probe to turn red