mirror of
https://github.com/fabriziosalmi/caddy-waf.git
synced 2026-07-30 14:25:56 -04:00
bfdb87bea4
add-package-guide.md said "v0.3.4 and earlier carry a high-severity denial-of-service (GHSA-gfj3-cmff-q8wh)". The advisory records the affected range as < 0.3.4, patched in 0.3.4, so v0.3.4 is the fix -- and the sentence contradicted its own follow-up. This was wrong security guidance in install documentation, not a typo. The same page linked installation.md#option-1-..., but that page numbers its sections "Method N", so the anchor never resolved. Root cause: README used "Option N" for the same install paths. README now uses "Method N" throughout. VitePress fails the build on a link to a missing page but does not check the fragment, so a stale anchor ships silently -- this one survived review and a green CI run. check-anchors.mjs validates every anchor against the target page's headings and runs as a predocs:build script. Verified it exits 1 on the broken anchor and 0 once fixed; an audit found no others. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
17 lines
464 B
JSON
17 lines
464 B
JSON
{
|
|
"name": "caddy-waf-docs",
|
|
"private": true,
|
|
"type": "module",
|
|
"description": "Documentation site for caddy-waf, built with VitePress.",
|
|
"scripts": {
|
|
"docs:dev": "vitepress dev docs",
|
|
"docs:check-anchors": "node docs/.vitepress/check-anchors.mjs",
|
|
"predocs:build": "npm run docs:check-anchors",
|
|
"docs:build": "vitepress build docs",
|
|
"docs:preview": "vitepress preview docs"
|
|
},
|
|
"devDependencies": {
|
|
"vitepress": "^1.6.4"
|
|
}
|
|
}
|