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-17
#10157
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 handoffPrivateEnclaveAudit(
+export function serializeFiniteSchema(schema: FiniteSchemaNode): FiniteSchemaWireNode {
+export const HOST_EXECUTOR_REJECTION_STAGES = Object.freeze([
+export function readGatewayReadinessResponse(
+export function requireObject(
+export async function writePrivateFile(
+export function resolveArtifactOwner(): { uid: number; gid: number } {
+export function openArtifactDirectory(directory: string): number {
+export function publishFinalResolvedConfig(directory: string, contents: string): void {
+export function publishEarlyResolvedConfig(contents: string): string {
🔎 Notable Findings
All five security-critical files are at or near full coverage: docker-manager.ts, host-iptables.ts, and squid-config.ts are 100% on every metric; domain-patterns.ts is 100% statements with 89.47% branches.
src/cli.ts has the weakest security-critical number: 50% branch coverage, though statements and functions are high.
Two files are flagged CRITICAL in the gaps brief: src/bounded-execution/finite-cardinality.ts (46% statements, 35% branches) and src/nvx/cleanup-registry.ts (48% statements, 39% branches). Neither is security-critical by the list above, but both are well below the 80% bar.
src/bounded-execution/finite-disclosure.ts has only 11.42% branch coverage, the lowest branch figure in the table.
Recent changes touch the bounded-execution, enclave, and resolved-config areas, which are the lowest-coverage parts of the codebase.
🎯 Recommendations
High: Add tests for src/bounded-execution/finite-cardinality.ts and src/nvx/cleanup-registry.ts, targeting the untested branches first (cardinality limit and cleanup failure paths). Aim for at least 80% statements and branches.
Medium: Add tests for the untested branches in src/cli.ts (currently 50%), focusing on option-validation and error paths, since this is the entry point for every firewall invocation.
Low: Raise branch coverage in src/bounded-execution/finite-disclosure.ts (11.42%) and src/microvm/network-reservation.ts (54.86%), and cover the new resolved-config-artifact.ts publish functions, which were added in the last 7 days.
Generated by test-coverage-reporter workflow. Trigger: schedule
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-17
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
docker-manager.ts,host-iptables.ts, andsquid-config.tsare 100% on every metric;domain-patterns.tsis 100% statements with 89.47% branches.src/cli.tshas the weakest security-critical number: 50% branch coverage, though statements and functions are high.src/bounded-execution/finite-cardinality.ts(46% statements, 35% branches) andsrc/nvx/cleanup-registry.ts(48% statements, 39% branches). Neither is security-critical by the list above, but both are well below the 80% bar.src/bounded-execution/finite-disclosure.tshas only 11.42% branch coverage, the lowest branch figure in the table.🎯 Recommendations
src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts, targeting the untested branches first (cardinality limit and cleanup failure paths). Aim for at least 80% statements and branches.src/cli.ts(currently 50%), focusing on option-validation and error paths, since this is the entry point for every firewall invocation.src/bounded-execution/finite-disclosure.ts(11.42%) andsrc/microvm/network-reservation.ts(54.86%), and cover the newresolved-config-artifact.tspublish functions, which were added in the last 7 days.Generated by test-coverage-reporter workflow. Trigger:
scheduleAll reactions