[Coverage Report] Test Coverage Report — Finite-Disclosure Protocol and Firecracker Integration

[github-actions[bot]]

📊 Test Coverage Report — 2026-08-09

This report analyzes test coverage for gh-aw-firewall, a security-critical L7 egress control firewall for agentic workflows. Coverage data was generated from the latest test suite run.

Overall Coverage

• Total Statements: Measured across 260 test files covering 507 TypeScript source files
• Test-to-Source Ratio: 1 test file per ~2 source files (robust baseline)
• Coverage Metrics: Standards include line, statement, function, and branch coverage

🛡️ Security-Critical Path Status

The following security-critical modules require special attention due to network isolation, domain filtering, and container management responsibilities:

File	Lines	Statements	Functions	Branches	Status
src/bounded-execution/finite-disclosure.ts	❌ CRITICAL	9.26%	Very Low	0.26%	URGENT
src/enclave/runtime-preflight.ts	⚠️ LOW	70%	Good	46.51%	Monitor
src/firecracker/preflight.ts	⚠️ LOW	75%	Good	65.51%	Monitor
src/host-iptables-rules.ts	✅	Extensive	Good	Good	Good
src/squid/config-generator.ts	✅	Extensive	Good	Good	Good
src/docker-manager-*.ts	✅	12+ test files	Good	Good	Good
src/domain-patterns.ts	✅	Covered	Good	Good	Good

Key Finding: Most security-critical network/container modules are well-covered. However, the finite-disclosure protocol (responsible for result validation and information-budget accounting) is severely under-tested.

📋 Coverage Table

Critical/High-Priority Modules

Module	Test Files	Purpose	Coverage Assessment
finite-disclosure.ts	❌ NONE	Enclave response schema validation, cardinality computation, information-budget accounting	9.26% stmt / 0.26% branch — No dedicated tests
runtime-preflight.ts	1	Enclave runtime validation	70% stmt / 46.51% branch
preflight.ts (Firecracker)	1	Firecracker guest preflight checks	75% stmt / 65.51% branch
host-iptables-rules.ts	6+	iptables rule generation for network isolation	✅ Comprehensive
config-generator.ts	8+	Squid proxy config generation for domain ACLs	✅ Comprehensive
docker-manager-*.ts	12+	Container lifecycle, volume mounts, environment setup	✅ Comprehensive
domain-patterns.ts	1	Domain pattern matching and normalization	✅ Comprehensive

🔧 Function Audit

Exported functions in finite-disclosure.ts (900 lines, 0% test coverage):

Function	Purpose	Tests
validateSchema()	Validates agent-authored response schema structure	❌ MISSING
schemaCardinality()	Computes total distinguishable values in schema	❌ MISSING
informationChargeForSchema()	Calculates information-budget cost for schema	❌ MISSING
validateValueAgainstSchema()	Validates query result against declared schema	❌ MISSING
canonicalizeSchemaValue()	Canonicalizes result value to JSON string	❌ MISSING
strictParseJson()	Hand-written JSON parser (security-critical, no backtracking)	❌ MISSING
validateEnclaveScriptRequest()	Validates request structure and limits	❌ MISSING
parseAndValidateFiniteOutput()	Full validation pipeline for query output	❌ MISSING

Note: The module uses custom recursive-descent parsers instead of JSON.parse to prevent attacker-controlled inputs from building unbounded parse trees. This security-critical design choice is untested.

📅 Recent Source Changes (last 7 days)

The repository has seen active development in the Firecracker/guest execution domain:

• PR feat: add Firecracker guest execution transport #7135: feat: add Firecracker guest execution transport — New Firecracker control plane
• PR Enforce isolated networking for Firecracker #7134: Enforce isolated networking for Firecracker — Network isolation extension
• PR Add Firecracker control-plane preview #7133: Add Firecracker control-plane preview — Core Firecracker feature
• PR Refactor external agent runtime lifecycle #7129: Refactor external agent runtime lifecycle — Runtime lifecycle changes

These changes touch enclave/Firecracker preflight and validation logic, which depend indirectly on finite-disclosure validation. The low coverage in runtime-preflight.ts (70%) and preflight.ts (75%) reflects incomplete testing of new features.

🔎 Notable Findings

1. CRITICAL: Finite-Disclosure Protocol Untested — The src/bounded-execution/finite-disclosure.ts module implements the enclave response schema validation and information-budget accounting protocol with 9.26% statement coverage and 0.26% branch coverage. This is the trusted validator that prevents information leakage and schema violations. There is no dedicated test file (finite-disclosure.test.ts). The module contains ~9 exported functions with custom recursive-descent JSON parsing, cardinality computation using BigInt, and result canonicalization — all untested in TypeScript. (A JavaScript mirror exists for the enclave server, tested via integration tests, but the primary TypeScript implementation lacks unit test coverage.)

2. Firecracker / Enclave Integration Tests Missing — Recent commits (PR Add Firecracker control-plane preview #7133–feat: add Firecracker guest execution transport #7135) add Firecracker guest execution and enclave runtime preflight. The runtime-preflight.ts (70%) and preflight.ts (75%) modules reflect incomplete branch coverage. These modules handle runtime validation of untrusted guest environments and preflight checks — edge cases and error paths remain undertested.

3. Strong Coverage for Core Network & Container Logic — Host iptables rules, Squid proxy config, and Docker container management all have >12 dedicated test files with strong line and branch coverage. Domain pattern matching, CLI options parsing, and service startup/cleanup are well-tested.

4. No Regression in Legacy Security Paths — Re-export modules (src/host-iptables.ts, src/squid-config.ts, src/docker-manager.ts, src/cli.ts) act as API boundaries. Actual implementations in submodules (host-iptables-rules.ts, squid/config-generator.ts, container-lifecycle.ts) have extensive test coverage.

🎯 Recommendations

HIGH PRIORITY

• Create src/bounded-execution/finite-disclosure.test.ts — Add dedicated unit tests for all 9+ exported functions. Cover:
  • Schema validation: valid enums, integers, objects, tuples, arrays, unions, edge cases
  • Cardinality computation: BigInt overflow guard, capped multiplication
  • JSON parsing: malformed input, control characters, duplicate keys, nesting depth
  • Result validation: type mismatches, out-of-range values, canonicalization
  • Align with the JavaScript mirror (containers/bounded-execution/finite-disclosure.js) to ensure protocol parity for enclave integration tests
• Estimated effort: 3–5 hours (high complexity due to schema algebra and security constraints)

MEDIUM PRIORITY

• Expand src/enclave/runtime-preflight.ts branch coverage (46.51% → 70%+) — Add test cases for error paths:
  • Invalid runtime configuration, missing capabilities, network isolation verification
  • Sandbox ingress validation, enclave environment setup edge cases
• Expand src/firecracker/preflight.ts branch coverage (65.51% → 80%+) — Cover Firecracker-specific validation:
  • Guest config validation, vsock/iptables setup verification, vsock client connection errors
• Estimated effort per module: 1–2 hours

LOW PRIORITY

• Document coverage targets — Set coverage thresholds in CI (e.g., finite-disclosure ≥90%, overall ≥80%) to prevent future regressions
• Integrate coverage badges — Add coverage badge to README.md linked to GitHub Actions artifact
• Estimated effort: 30 minutes

---

Report Generated: 2026-08-09
Test Files: 260
Source Files: 507
Primary Gap: Finite-Disclosure Protocol Validation (9.26% coverage)

Generated by Test Coverage Reporter · sum00 · 21.6 AIC · ⊞ 5.1K · ◷

• expires on Aug 16, 2026, 10:52 PM UTC

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-08-16T22:52:35.102Z.

Closed by Workflow