AgentBlindspot v0.1.0
AgentBlindspot is a local-first evidence analyzer for AI coding workflows. It joins Git changes, repository dependency structure, observed coding-agent tool activity, and optional coverage so reviewers can see potentially affected files with no observed inspection or direct verification evidence.
What is in 0.1.0
- Deterministic JS/TS and Python file/module dependency graphs.
- Codex, Claude Code, and OpenCode evidence adapters.
- Worktree and commit-range analysis.
- LCOV, Istanbul/nyc JSON, and coverage.py JSON ingestion.
- Explicit changed / inspected / directly verified / possible blind spot / unknown states.
- Standalone JSON and no-CDN HTML reports.
- Large-report bounded rendering while preserving the full machine-readable finding set.
doctor,adapters, andschemaCLI surfaces.- Reproducible auth-redirect demonstration and deterministic fixtures.
- Cross-platform CI, installed-package smoke, CodeQL/SARIF, performance gates, and real Chromium report smoke.
The key boundary
A possible blind spot is an attention signal, not proof of a bug. An uninspected dependent may be completely safe, and a fully inspected/tested change can still contain a defect outside the modeled graph.
AgentBlindspot reports evidence, inference, and uncertainty separately rather than using missing evidence as a defect verdict.
Run the CLI from this release
Node.js 22+ and Git are required. The package is not published to the npm registry.
Download agent-blindspot-0.1.0.tgz from the assets below, extract it, and run the built CLI directly:
tar -xzf agent-blindspot-0.1.0.tgz
node package/dist/apps/cli/src/index.js --version
node package/dist/apps/cli/src/index.js analyze . --agent claude --session ./session.jsonGitHub Releases is the authoritative v0.1.0 CLI distribution channel.
JSR library package
The library/module surface is also published separately as @aprashnasuraj-dev/agent-blindspot@0.1.0 on JSR:
https://jsr.io/@aprashnasuraj-dev/agent-blindspot@0.1.0
It was published through GitHub Actions OIDC from source commit 89e0252e7a60f8d13219630f85e0c8ef6061a9c9 and emitted Sigstore provenance. The JSR package does not replace the GitHub-hosted CLI artifact.
Supply-chain evidence
This GitHub release points to exact commit b1014573264feab70cebc198e24e4598a414c65d.
The attached tarball was rebuilt from that exact commit, smoke-tested in an isolated consumer directory, and matched the pre-recorded SHA-256:
5a5f94b6c395a56865068b9a54c11c875a74fd034ae988467b42da0f705292aa
package-evidence.json and SHA256SUMS.txt are attached alongside the tarball.
Security and privacy
V1 is local-first and performs no telemetry/report network calls. Raw transcript prose and binary/Base64 content are not retained by default. Repository path escapes are rejected; standalone HTML escapes untrusted strings and uses a restrictive CSP.
See SECURITY.md, docs/EVIDENCE_MODEL.md, docs/COMPATIBILITY.md, and docs/KNOWN_LIMITATIONS.md for the exact evidence and trust boundaries.