DeploySutra AI · offline static analysis · no cluster was contacted

Independent audit report

Everything below was measured when you ran it, not written by hand.

Totals

49checks
42passed
0failed
7not run

Generated 2026-11-17T17:13:23.810Z · measured on this machine at run time.

Automated test suite

PASS The repository test suite executed as a child process; counts are parsed from its TAP output.

Automated test suite
CheckResultDetail
node --test suitePASS312 tests: 308 passed, 0 failed, 4 skipped

Rule accuracy on the labelled corpus

PASS 50 author-labelled cases. This is a regression corpus, not an independent benchmark: it shows the rules do what they claim on these inputs, not that they catch every real misconfiguration.

Rule accuracy on the labelled corpus
CheckResultDetail
Corpus precisionPASS100.0% (32 TP, 0 FP)
Corpus recallPASS100.0% (0 FN)
Every case matches exactlyPASS50/50 cases (31 positive, 19 negative twins)
Every per-document rule has a positive casePASS18/18 rules exercised
Diff-level rule DS-K8S-019 (resource removed)PASSa resource missing from AFTER is reported

Secret and state leakage

PASS Canary strings were planted in every place a secret could plausibly be copied from, then the produced reports were searched for them.

Secret and state leakage
CheckResultDetail
Env password, Secret data and annotation token never reach report JSONPASS3 canaries planted in BEFORE and AFTER; 0 found
Plan variables, prior_state, values and addresses never reach plan summaryPASScanaries in variables, prior_state, before/after and address; 0 found
Secret-like env literal is flagged without echoing the valuePASSDS-K8S-012 raised, value withheld
Diffs mark redacted fields as redactedPASS2 redacted field change(s)
Discarded plan sections are named, not copiedPASSprior_state, variables
Shipped example reports contain no token-shaped stringsPASSexamples/reports scanned for GitHub/npm/AWS/private-key shapes

Hostile and malformed input

PASS_WITH_NOT_RUN Untrusted manifests are data. The parser must fail loudly, never skip, never hang.

Hostile and malformed input
CheckResultDetail
Unsupported YAML constructs fail explicitlyPASS15/15 hostile inputs rejected with an Error
Mutation fuzz (400 inputs, fixed seed)PASS0 non-Error crashes, 0 parses over 500 ms
Deeply nested input is handledPASS400 nesting levels handled without a stack overflow
Input over 1 MiB is refusedPASSreadManifests rejects >1 MiB
Non-manifest extension is refusedPASS.txt rejected
Symlinked input is refusedNOT_RUNthis OS user cannot create symlinks (Windows without Developer Mode); covered on Linux/macOS CI

Evidence integrity and gate safety

PASS SHA-256 seals are tamper evidence, not signatures. The gate has exactly two states.

Evidence integrity and gate safety
CheckResultDetail
Equal inputs give an identical digest (deterministic)PASS29ec76d7a2a7beb0…
Digest survives a JSON round tripPASSverify(JSON.parse(JSON.stringify(report))) is true
Edited gate is detectedPASSBLOCKED → READY edit rejected
Added field is detectedPASSextra property rejected
Removed seal is detectedPASSreport without integrity rejected
No input can produce a READY gatePASS50 corpus resources assessed with every rollback box ticked; gates seen: HUMAN_REVIEW_REQUIRED, BLOCKED
Declared rollback evidence is never "ready"PASSall five declarations → DECLARED_NOT_VERIFIED, ready=false

Static safety review of the source

PASS Regex scans of the shipped code. They prove absence of these patterns, not absence of every possible vulnerability.

Static safety review of the source
CheckResultDetail
No subprocess APIs in shipped packagesPASSchild_process appears only in the audit runner itself (it runs the test suite and the CLI help)
No dynamic code executionPASSno eval / new Function
No outbound network callsPASSno fetch/https/net/dgram usage
Only the loopback report server listens on a socketPASSnode:http and listen() appear only in packages/server/index.mjs
CLI exposes no deploy/apply/destroy/rollback/exec/sync commandPASSnone listed in `deploysutra help`
No token-shaped strings in the shipped sourcePASS14 source files scanned
Core has zero runtime dependenciesPASSpackage.json has no "dependencies"

Performance budgets

PASS Median of 5 runs on this machine. Budgets are deliberately loose guardrails against regressions, not benchmarks of other hardware.

Performance budgets
CheckResultDetail
assess() 200 resources before/afterPASSmedian 37 ms (budget 3000 ms)
parse 200 documentsPASSmedian 12 ms (budget 2000 ms)
rules over 200 resourcesPASSmedian 1 ms (budget 1000 ms)

Package and instruction assets

PASS Structural checks that the shipped package is internally consistent.

Package and instruction assets
CheckResultDetail
package.json version matches VERSION constantPASS0.2.0
bin targets existPASSdeploysutra, deploysutra-ai
files[] entries existPASS21 entries
25 portable skills with valid frontmatterPASS25 skills, 25 valid frontmatter
Every skill declares what deterministic command/rule backs itPASS25/25 carry a "Backed by" line
20 agent roles registered with files on diskPASS25 role definitions
8 workflows and 10 safety rule filesPASS8 workflows, 10 rules
License and notices presentPASSLICENSE, NOTICE, SECURITY.md, CHANGELOG.md

Explicitly not run

NOT_RUN Listed so nobody mistakes absence of a result for a pass.

Explicitly not run
CheckResultDetail
Live cluster dry-run (kubectl diff / --dry-run=server)NOT_RUNby design: needs credentials; never run automatically
MCP Inspector / third-party MCP clientNOT_RUNMCP server verified with a scripted JSON-RPC client only
Native activation of skills in each IDENOT_RUNskills are copied, not proven to be loaded by each host
Independent third-party benchmark of the rulesNOT_RUNonly the author-labelled corpus exists
Signed releasesNOT_RUNnpm provenance only if published via CI; reports carry unkeyed checksums, not signatures
macOS / Windows results from this runNOT_RUNonly win32 was measured here; see CI for the matrix

Environment

Where this ran
KeyValue
tooldeploysutra-ai 0.2.0
nodev24.15.0
platformwin32 10.0.26300
archx64
cpus14
offlineno network access was used

Reproduce it yourself

npm ci --ignore-scripts   # no dependencies, so this only checks the lockfile-free install
npm test
npx deploysutra-ai audit --out audit-out
node packages/cli/index.mjs verify --report audit-out/audit-report.json

Honest limits