Skip to content

docs: canonical dependency-security consensus plan - #14

Merged
mereditharmcgee merged 1 commit into
mainfrom
docs/dependency-security-plan
Aug 29, 2026
Merged

docs: canonical dependency-security consensus plan#14
mereditharmcgee merged 1 commit into
mainfrom
docs/dependency-security-plan

Conversation

@mereditharmcgee

Copy link
Copy Markdown
Owner

Two-agent review (Codex brief → Claude independent review → two reconciliation rounds) reached consensus on resolving the current npm advisories.

docs/DEPENDENCY-SECURITY-PLAN.md is canonical. The brief and the review are retained for provenance with SUPERSEDED headers — do not work from either.

The plan

  • Stage 1 — compatible refresh within Astro 5. Vitest 4.1.x clears the critical; Resend 6.25.0 drops the svix/uuid chain. Plus dependency reclassification and a full-graph critical-severity CI audit gate.
  • Stage 2 — Astro 7.2.9, floor 7.1.0. GHSA-4g3v affects 7.0.9 inclusive, so no 7.0.x is a safe stopping point. Astro 6 is not a valid intermediate: three advisories affect 6.4.6 with no backport.
  • Standing rule — stay on the current Astro major. Across all six Astro-family advisories examined, every fix landed on the then-current major and none was backported.

Two things worth reading

The Astro 5.18.2 bump in Stage 1 is hygiene, not remediation — no 5.x fix exists for either Astro advisory. The branch summary must say so rather than implying the advisories are addressed.

Every affected advisory is currently unreachable in this codebase. The conditions being relied upon (no View Transitions, no astro:assets, no dynamic slot names, no image allowlist, the Cloudflare adapter's ASSETS binding) are recorded in §7 so a future change violating one is recognized as a security event rather than a feature.

All advisory ranges were verified against the GitHub Advisory Database and the npm registry, not taken from either agent's summary.

Docs only, no build impact. Implementation not started.

🤖 Generated with Claude Code

Two-agent review (Codex brief, Claude independent review, two reconciliation
rounds) reached consensus on how to resolve the current npm advisories.

docs/DEPENDENCY-SECURITY-PLAN.md is canonical and internally consistent:

- Stage 1: compatible refresh within Astro 5 (Vitest 4.1.x clears the critical,
  Resend 6.25.0 drops the svix/uuid chain), dependency reclassification, and a
  full-graph critical-severity CI audit gate.
- Stage 2: Astro 7.2.9, floor 7.1.0. GHSA-4g3v affects 7.0.9 inclusive, so no
  7.0.x is a safe stopping point. Astro 6 is not a valid intermediate: three
  advisories affect 6.4.6 with no backport.
- Standing rule: stay on the current Astro major. Across all six Astro-family
  advisories examined, every fix landed on the then-current major and none was
  backported.

The Astro 5.18.2 bump is hygiene, not remediation — no 5.x fix exists for either
Astro advisory, and the branch summary must say so.

All advisory ranges verified against the GitHub Advisory Database and npm
registry, not taken from either agent's summary. Every affected advisory is
currently unreachable in this codebase; the reachability conditions being relied
upon are recorded in §7 so that a future change which violates one is recognized
as a security event rather than a feature.

The brief and the review are retained for provenance with SUPERSEDED headers.
Do not work from either.

Docs only, no build impact. Implementation not started.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying ratemyplace with  Cloudflare Pages  Cloudflare Pages

Latest commit: 83b22d9
Status: ✅  Deploy successful!
Preview URL: https://924d84f4.ratemyplace-64y.pages.dev
Branch Preview URL: https://docs-dependency-security-pla.ratemyplace-64y.pages.dev

View logs

@mereditharmcgee
mereditharmcgee merged commit 39662a4 into main Aug 29, 2026
2 checks passed
@mereditharmcgee
mereditharmcgee deleted the docs/dependency-security-plan branch August 29, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant