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
#10446
Security-critical files are well covered:host-iptables.ts, squid-config.ts, and docker-manager.ts are at 100% across statements, branches, and functions. domain-patterns.ts is at 100% statements and functions, with 89.47% branches (2 if-branches and 1 switch-branch are the likely uncovered paths).
src/cli.ts branch coverage is 50%, despite being marked OK. It is the main orchestration entry point, so its untaken branches deserve review even though statement coverage is 87.5%.
13 files are below 80%, including 3 below 50% statements (finite-cardinality.ts, cleanup-registry.ts, resolved-config-artifact.ts). None of these are on the security-critical list, but they are in the bounded-execution, nvx, and config-artifact code paths.
finite-disclosure.ts has 11.42% branch coverage, the lowest branch figure in the report.
🎯 Recommendations
High: Add branch tests for src/cli.ts. Raise branch coverage from 50% toward 80%+, since it is the orchestration entry point. Focus on error and signal-handling paths.
Medium: Close the domain-patterns.ts branch gap (89.47%). Add tests for the uncovered if and switch branches, using invalid and edge-case domain inputs, to keep ACL validation fully exercised.
Medium: Raise src/bounded-execution/finite-cardinality.ts, src/nvx/cleanup-registry.ts, and src/resolved-config-artifact.ts above 60%. Start with the ❌ files, then finite-disclosure.ts's 11.42% branch coverage.
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% across statements, branches, and functions.domain-patterns.tsis at 100% statements and functions, with 89.47% branches (2 if-branches and 1 switch-branch are the likely uncovered paths).src/cli.tsbranch coverage is 50%, despite being marked OK. It is the main orchestration entry point, so its untaken branches deserve review even though statement coverage is 87.5%.finite-cardinality.ts,cleanup-registry.ts,resolved-config-artifact.ts). None of these are on the security-critical list, but they are in the bounded-execution, nvx, and config-artifact code paths.finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report.🎯 Recommendations
src/cli.ts. Raise branch coverage from 50% toward 80%+, since it is the orchestration entry point. Focus on error and signal-handling paths.domain-patterns.tsbranch gap (89.47%). Add tests for the uncovered if and switch branches, using invalid and edge-case domain inputs, to keep ACL validation fully exercised.src/bounded-execution/finite-cardinality.ts,src/nvx/cleanup-registry.ts, andsrc/resolved-config-artifact.tsabove 60%. Start with the ❌ files, thenfinite-disclosure.ts's 11.42% branch coverage.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions