feat: publish security & permanence audit, correct false readiness claims#21
Merged
Conversation
Adds /security-audit.html: the full Traverse Permanence & Security Audit (July 2026) -- verdict, 15-item findings register with severity, the permanence guarantee matrix, crate maturity table, trust boundary map, and the opportunity roadmap. Content is reproduced faithfully from the source audit; no numbers or claims invented. Linked from the Developers nav dropdown, mobile menu, and footer so it isn't orphaned. Also corrects claims elsewhere on the site that the audit contradicts: - roadmap.astro claimed "100% test coverage, all shipped code is tested, no exceptions." The audit found only 3 of 6 crates are coverage-gated; the CLI's ~9k-line HTTP surface and the MCP server are not. Corrected to state this precisely, linking to the audit. - is-traverse-production-ready.astro (both the visible body and its FAQPage JSON-LD) claimed the MCP server and CLI were safe to "use in production today" with no caveat. The audit found the MCP stdio server has zero authentication (any stdin writer can execute capabilities and read full traces) and the HTTP server defaults to Development mode with unverified JWTs. Added a "Known security gaps" section and corrected the safe-to-use list to reflect this. - what-is-traverse-security-model.astro implied checksums are verified automatically before deploy; the audit found the runtime checksum gate is not enforced in verify_artifact and Sigstore verification is a stub. Corrected the claim and added a pointer to the full audit. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/security-audit.html: the full Traverse Permanence & Security Audit (July 2026) — verdict, 15-item findings register with severity badges, permanence guarantee matrix, crate maturity table, trust boundary map, and opportunity roadmap. Content reproduced faithfully from the source audit, no numbers invented. Linked from the Developers nav dropdown, mobile menu, and footer.roadmap.astroclaimed "100% test coverage, no exceptions" — only 3/6 crates are actually coverage-gated (CLI's ~9k-line HTTP surface and MCP are not). Corrected.is-traverse-production-ready.astro(visible body and its FAQPage JSON-LD) said the MCP server and CLI were safe for production with no caveat — the audit found MCP has zero authentication and the HTTP server defaults to an insecure Development mode. Added a "Known security gaps" section.what-is-traverse-security-model.astroimplied checksums are verified automatically before deploy — the runtime checksum gate isn't actually enforced and Sigstore verification is a stub. Corrected and linked to the full audit.Test plan
🤖 Generated with Claude Code