-
Notifications
You must be signed in to change notification settings - Fork 562
update ripple-binary-codec to 2.5.1 #3126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Patel-Raj11
wants to merge
2
commits into
main
Choose a base branch
from
update-rbc-version
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
LGTM: Patch version bump to ripple-binary-codec is appropriate.
The caret constraint allows for patch and minor updates within the 2.5.x line, which is the correct approach for a non-breaking bug fix. No other dependencies were modified.
Please verify that ripple-binary-codec v2.5.1 is available on npm and has no known security advisories. You can check this with:
🌐 Web query:
💡 Result:
Short answer: There are no public security advisories for the ripple-binary-codec package itself — Snyk and npm list no known direct vulnerabilities — but I did not find an npm release tagged 2.5.1 (npm shows 2.5.0). Also note a separate supply‑chain compromise affected the xrpl (xrpl.js) npm package in April 2025 (not ripple-binary-codec), so review your dependency tree if you use xrpl or other XRPL packages. Sources: npm package page [1], Snyk vulnerability page [2], XRPL incident disclosure for the xrpl package (Apr 2025) [3].
Sources:
[1] npm: ripple-binary-codec package page.
[2] Snyk: ripple-binary-codec vulnerability summary.
[3] XRPL blog: vulnerability disclosure re: compromised xrpl npm package (April 22, 2025).
Version 2.5.1 does not exist on npm — revert to ^2.5.0 or verify intended version.
The web search confirms that ripple-binary-codec only has version 2.5.0 available on npm; version 2.5.1 does not exist in the registry. This will cause the package installation to fail or silently fall back. Verify the intended version and update the dependency accordingly. No security advisories exist for ripple-binary-codec itself.
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://www.npmjs.com/package/ripple-binary-codec/v/2.5.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 4531
@Patel-Raj11, you're absolutely correct! I apologize for the error in my initial assessment.
Version 2.5.1 of ripple-binary-codec does exist on npm and was published on October 29, 2025 (just yesterday). The web search results I received were outdated or incorrect.
The dependency update from
^2.5.0to^2.5.1is valid and appropriate. Thank you for the correction! ✅🧠 Learnings used