Skip to content

[Snyk] Fix for 5 vulnerabilities#472

Open
revan-zhang wants to merge 1 commit into
masterfrom
snyk-fix-4dcdc30b4af6f44fd3399b3b582d2510
Open

[Snyk] Fix for 5 vulnerabilities#472
revan-zhang wants to merge 1 commit into
masterfrom
snyk-fix-4dcdc30b4af6f44fd3399b3b582d2510

Conversation

@revan-zhang
Copy link
Copy Markdown
Contributor

@revan-zhang revan-zhang commented Apr 19, 2026

snyk-top-banner

Snyk has created this PR to fix 5 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • packages/example/package.json
  • packages/example/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Arbitrary Code Injection
SNYK-JS-PROTOBUFJS-16094665
  725  
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-STABLELIBED25519-15914262
  655  
medium severity Improper Removal of Sensitive Information Before Storage or Transfer
SNYK-JS-FOLLOWREDIRECTS-16032162
  545  
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  540  
medium severity Insufficient Visual Distinction of Homoglyphs Presented to User
SNYK-JS-BASEX-10118294
  495  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Arbitrary Code Injection


Open in Devin Review

@revan-zhang
Copy link
Copy Markdown
Contributor Author

revan-zhang commented Apr 19, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

Open in Devin Review

"@codemirror/lint": "^6.8.0",
"@cosmjs/amino": "^0.32.3",
"@cosmjs/stargate": "^0.32.4",
"@cosmjs/stargate": "^0.33.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 @cosmjs/amino not bumped alongside @cosmjs/stargate, causing duplicate incompatible versions

The PR bumps @cosmjs/stargate from ^0.32.4 to ^0.33.0, but leaves @cosmjs/amino at ^0.32.3. Since @cosmjs/stargate@0.33.1 (the resolved version) depends on @cosmjs/amino@^0.33.1, the dependency tree now contains two incompatible versions of @cosmjs/amino: 0.32.4 (from the direct dependency) and 0.33.1 (pulled in transitively by stargate). The same duplication cascades to @cosmjs/crypto, @cosmjs/encoding, @cosmjs/math, and @cosmjs/utils as confirmed in the yarn.lock. These are sibling packages from the same monorepo designed to work together at matching versions. If any code (even transitively, e.g. through secretjs or future direct usage) passes amino types between the 0.32 and 0.33 trees, it can cause subtle runtime failures due to instanceof checks or type mismatches.

Suggested change
"@cosmjs/stargate": "^0.33.0",
"@cosmjs/stargate": "^0.33.0",
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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.

2 participants