You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-09
#9738
Security-critical files are at or near full coverage: host-iptables.ts, squid-config.ts, and docker-manager.ts are at 100% across statements, branches, and functions.
Remaining security-path gaps are branch-level: src/cli.ts has 50% branch coverage and src/domain-patterns.ts has 89.47% branch coverage.
Two files are critical: src/nvx/cleanup-registry.ts (42.8% statements, 32.11% branches) and src/bounded-execution/finite-cardinality.ts (46.03% statements, 35.29% branches).
Low branch coverage in src/bounded-execution/finite-disclosure.ts: 11.42% branch coverage, the weakest branch metric in the report.
🎯 Recommendations
High: Add tests for src/nvx/cleanup-registry.ts and src/bounded-execution/finite-cardinality.ts, focusing on the uncovered statements and branches listed in the coverage gaps brief.
High: Add branch tests for src/cli.ts (50% branch coverage) covering the untested option and error paths, since it is the orchestration entry point.
Medium: Add tests for src/domain-patterns.ts to cover the remaining branches (89.47%), prioritizing domain validation edge cases.
Low: Raise branch coverage in src/bounded-execution/finite-disclosure.ts (11.42%) and the other files in the 50–60% range (network-reservation.ts, finite-schema.ts).
Generated by test-coverage-reporter workflow. Trigger: push
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts, anddocker-manager.tsare at 100% across statements, branches, and functions.src/cli.tshas 50% branch coverage andsrc/domain-patterns.tshas 89.47% branch coverage.src/nvx/cleanup-registry.ts(42.8% statements, 32.11% branches) andsrc/bounded-execution/finite-cardinality.ts(46.03% statements, 35.29% branches).src/bounded-execution/finite-disclosure.ts: 11.42% branch coverage, the weakest branch metric in the report.🎯 Recommendations
src/nvx/cleanup-registry.tsandsrc/bounded-execution/finite-cardinality.ts, focusing on the uncovered statements and branches listed in the coverage gaps brief.src/cli.ts(50% branch coverage) covering the untested option and error paths, since it is the orchestration entry point.src/domain-patterns.tsto cover the remaining branches (89.47%), prioritizing domain validation edge cases.src/bounded-execution/finite-disclosure.ts(11.42%) and the other files in the 50–60% range (network-reservation.ts,finite-schema.ts).Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions