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-13
#9950
src/agent-entrypoint-output.test.ts
src/agent-helper-staging.test.ts
src/agent-runtime-start.test.ts
src/agent-runtime-start.ts
src/api-proxy-config-domains.test.ts
src/api-proxy-config-domains.ts
src/api-proxy-config-validation.test.ts
src/api-proxy-config-validation.ts
src/api-proxy-config-warnings.test.ts
src/api-proxy-config-warnings.ts
---
+export function parseDeviceAcl(contents: string): string[] {
+export function deviceAclArgument(entries: readonly string[]): string {
+export function sameDeviceAcl(
+export function withCloudHypervisorDeviceAclLock<T>(
+export function withNvxDeviceAclLock<T>(
+export function addGithubTokenEnvVars(excludedEnvVars: Set<string>): void {
+export function getGithubTokenEnvValues(): (string | undefined)[] {
+export function assertNoHostGithubTokenValue(
+export function enforceGithubTokenIsolation(
+export function buildMicrovmScratchInit(scratchMib: number, supervisorGuestPath: string): string {
🔎 Notable Findings
All five security-critical files (host-iptables.ts, squid-config.ts, domain-patterns.ts, docker-manager.ts, cli.ts) meet their targets; host-iptables.ts, squid-config.ts, and docker-manager.ts are at 100% across all metrics.
src/cli.ts has only 50% branch coverage, the weakest point on the critical path.
src/bounded-execution/finite-cardinality.ts (46% statements) and src/nvx/cleanup-registry.ts (48% statements) are the lowest-covered files in the repo.
src/bounded-execution/finite-disclosure.ts has 11.42% branch coverage, the lowest branch figure in the table.
Recent changes added new device-ACL and GitHub-token isolation helpers; no coverage data for these was flagged in the brief.
🎯 Recommendations
High: Add branch tests for src/cli.ts (50% branch coverage) covering error and option-validation paths, since it is the orchestration entry point.
High: Add unit tests for src/bounded-execution/finite-cardinality.ts and src/nvx/cleanup-registry.ts (both below 50% statements), prioritizing the cleanup and cardinality-limit paths.
Medium: Raise branch coverage in src/bounded-execution/finite-disclosure.ts (11.42%) and verify the new GitHub-token isolation and device-ACL helpers have direct tests.
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-13
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts,domain-patterns.ts,docker-manager.ts,cli.ts) meet their targets;host-iptables.ts,squid-config.ts, anddocker-manager.tsare at 100% across all metrics.src/cli.tshas only 50% branch coverage, the weakest point on the critical path.src/bounded-execution/finite-cardinality.ts(46% statements) andsrc/nvx/cleanup-registry.ts(48% statements) are the lowest-covered files in the repo.src/bounded-execution/finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the table.🎯 Recommendations
src/cli.ts(50% branch coverage) covering error and option-validation paths, since it is the orchestration entry point.src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts(both below 50% statements), prioritizing the cleanup and cardinality-limit paths.src/bounded-execution/finite-disclosure.ts(11.42%) and verify the new GitHub-token isolation and device-ACL helpers have direct tests.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions