docs(reference): add third-party audit summary page - #119
Open
theo372001 wants to merge 1 commit into
Open
Conversation
…otocol#86) Summarizes the Stellar Asset Contract (SAC) compatibility review for non-technical readers, with severity, findings, and remediation status per finding, and a link to the raw report in contracts/stellar/audits. Also fixes a pre-existing invalid-JSON syntax error in the docs.json Reference nav group (duplicate/malformed pages key from a bad merge in 5c5c7f1 / 23d0a1f) and adds the new audits page's nav entry.
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
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
Adds a curated, non-technical summary page for Wraith Protocol's contract audits, per #86.
reference/audits.mdx— one section per audit with firm, date, scope, findings summary (severity + description per finding), and remediation status, linking to the raw report.docs.json.pageskey left over from a bad merge in5c5c7f1/23d0a1f, which brokedocs.jsonparsing entirely (unrelated content, e.g.contracts/evm/contracts/stellar/etc., remains reachable via the separate, untouched "Contracts" group). Had to fix it since it's the exact object this PR's nav entry needed to go into.Type
Related Issue
Closes #86
Testing
node -e "JSON.parse(...)"ondocs.json: now valid (was failing before this fix).mint validate: the only remaining failures are pre-existing and unrelated, confirmed viagit stashcomparison against cleandevelop— a genuine MDX parse error incontracts/stellar.mdx(stray!character) and a dangling nav reference toreference/stellar-event-schemas, a file that has never existed in the repo. My newreference/auditsentry produces zero warnings.mint broken-linkscouldn't complete, blocked by the same pre-existingcontracts/stellar.mdxparse error.contracts/stellar/audits/2026-06-sac-compatibility.md) for firm name, date, and all 7 finding IDs/severities.