Repository navigation
fix: remediate vulnerable build and MCP test dependencies - #12
Merged
Merged
Conversation
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.
Scope
Fix the six open Dependabot alerts for devalue, plus six additional vulnerable dependency versions found by the full development/production audit. No audit exceptions, major-version upgrades, payment code, or application feature changes.
Keep the production MCP server on its existing major version and stdio/read-only boundary. Update generated third-party notices and the exact pnpm overrides/lockfile.
Verification
Boundaries and limitations
This is a dependency/build release, not a claim that every advisory is reachable from public visitors. BLACKPROOF remains a static, local-first AGPL application with no document-upload server.
The http-cache-semantics advisory currently declares versions through 4.2.0 affected but names no patched version. Official 4.3.0 improves Vary handling; it does not rewrite the separately disputed max-stale behavior. Astro's actual consumer does not use that cache-reuse method or forward Set-Cookie, and private/no-store responses receive no reusable expiry. Do not describe this as a universal max-stale algorithm fix.
magicast contains a bundled legacy source-map implementation inside its build-time configuration transformer; a pnpm override cannot rewrite embedded code. Its path is not part of the served static application and no user upload reaches it. Active source-map-js package consumers resolve to 1.2.2.
Production must use the exact successful main-branch CI artifact with verified GitHub provenance, manifest and transfer checksums, followed by operator-run atomic activation and separate HTTPS verification.