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-22
#10444
Security-critical files are healthy:host-iptables.ts, squid-config.ts, and docker-manager.ts are at 100% statements/branches/functions; domain-patterns.ts is at 100% statements with 89.47% branch coverage.
src/cli.ts has the weakest security-adjacent coverage: 87.5% statements and only 50% branch coverage, despite 100% function coverage. It is the main orchestration entry point, so the untested branches are likely error and signal-handling paths.
Three files are critically low (<50% statements):bounded-execution/finite-cardinality.ts, resolved-config-artifact.ts, and nvx/cleanup-registry.ts. None are in the security-critical list, but cleanup-registry.ts handles resource teardown.
bounded-execution/finite-disclosure.ts has 11.42% branch coverage, the lowest branch figure in the report, with 37.5% function coverage.
Recent churn is concentrated in new modules: the last 7 days added or changed API-proxy config, agent entrypoint, and runtime-start files, plus shared test-helper mocks.
🎯 Recommendations
High: add branch tests for src/cli.ts. Cover the error and signal-handling branches (SIGINT/SIGTERM, failed container startup, non-zero exit propagation). Target: branch coverage ≥ 80%.
Medium: raise resolved-config-artifact.ts, bounded-execution/finite-cardinality.ts, and nvx/cleanup-registry.ts above 70% statements. Start with cleanup-registry.ts, since failed cleanup can leave orphaned resources. Prioritize the uncovered functions (60–66% function coverage).
Low: add branch tests for bounded-execution/finite-disclosure.ts (11.42% branch) and the microvm/network-reservation.ts edge cases (54.86% branch). Keep domain-patterns.ts at its current level, but add tests for its two uncovered if branches and its one switch branch.
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.
📊 Test Coverage Report — 2026-10-22
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% statements/branches/functions;domain-patterns.tsis at 100% statements with 89.47% branch coverage.src/cli.tshas the weakest security-adjacent coverage: 87.5% statements and only 50% branch coverage, despite 100% function coverage. It is the main orchestration entry point, so the untested branches are likely error and signal-handling paths.bounded-execution/finite-cardinality.ts,resolved-config-artifact.ts, andnvx/cleanup-registry.ts. None are in the security-critical list, butcleanup-registry.tshandles resource teardown.bounded-execution/finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report, with 37.5% function coverage.🎯 Recommendations
src/cli.ts. Cover the error and signal-handling branches (SIGINT/SIGTERM, failed container startup, non-zero exit propagation). Target: branch coverage ≥ 80%.resolved-config-artifact.ts,bounded-execution/finite-cardinality.ts, andnvx/cleanup-registry.tsabove 70% statements. Start withcleanup-registry.ts, since failed cleanup can leave orphaned resources. Prioritize the uncovered functions (60–66% function coverage).bounded-execution/finite-disclosure.ts(11.42% branch) and themicrovm/network-reservation.tsedge cases (54.86% branch). Keepdomain-patterns.tsat its current level, but add tests for its two uncoveredifbranches and its oneswitchbranch.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions