Repository navigation
Update vulnerable interface dependencies - #429
Merged
Merged
Conversation
✅ Deploy Preview for pintomoney ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
The current dependency tree has 148 registry advisory/version matches, including 6 critical matches. This updates vulnerable browser and tooling packages, refreshes compatible transitive dependencies, and removes three unused integrations. The resulting audit has 12 matches: 0 critical, 5 high, 6 moderate, and 1 low.
docs/dependency-security-updates.md, including advisory links and override rationale.This is a dependency-focused review, not an exhaustive application or smart-contract audit. Registry matches do not establish production exploitability. The MetaMask historical debug advisory remains, but debug 4.4.2 is not selected by the lockfile. No source-confirmed production exploit was established in the reviewed paths.
Validation: immutable Yarn install, all 108 tests, production build, minimal offline GraphQL codegen, and local Silo/wallet-chooser browser smoke pass. An independent dependency-diff review found no blocking regression. TypeScript reports the same 15 diagnostics as the unchanged baseline. Full live codegen is blocked by cache internal-server and pintostalk indexing errors reproduced on the baseline; Pinto and Exchange schema generation succeeds. No signing or authenticated wallet flows were tested.
Separate from the Silo-value fix in #428. Authored and committed as
FordPinto <fordpinto@pintofarm.org>; published usingfordpintomoney.