[Snyk] Fix for 5 vulnerabilities#472
Conversation
…duce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-PROTOBUFJS-16094665 - https://snyk.io/vuln/SNYK-JS-STABLELIBED25519-15914262 - https://snyk.io/vuln/SNYK-JS-FOLLOWREDIRECTS-16032162 - https://snyk.io/vuln/SNYK-JS-ELLIPTIC-14908844 - https://snyk.io/vuln/SNYK-JS-BASEX-10118294
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
| "@codemirror/lint": "^6.8.0", | ||
| "@cosmjs/amino": "^0.32.3", | ||
| "@cosmjs/stargate": "^0.32.4", | ||
| "@cosmjs/stargate": "^0.33.0", |
There was a problem hiding this comment.
🟡 @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.
| "@cosmjs/stargate": "^0.33.0", | |
| "@cosmjs/stargate": "^0.33.0", |
Was this helpful? React with 👍 or 👎 to provide feedback.
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.jsonpackages/example/yarn.lockNote 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 runyarnto update the contents of the./yarn/cachedirectory.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:
SNYK-JS-PROTOBUFJS-16094665
SNYK-JS-STABLELIBED25519-15914262
SNYK-JS-FOLLOWREDIRECTS-16032162
SNYK-JS-ELLIPTIC-14908844
SNYK-JS-BASEX-10118294
Important
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