Skip to content

Conversation

@lklimek
Copy link
Contributor

@lklimek lklimek commented Apr 25, 2025

Issue being fixed or feature implemented

Elliptic older than 6.6.0 was affected by a security issue.

What was done?

Updated Elliptic to 6.6.1 and un-ignored it.

Ran yarn install to update caches.

How Has This Been Tested?

GHA

Breaking Changes

None

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

Summary by CodeRabbit

  • Chores
    • Updated the "elliptic" package to version 6.6.1.
    • Removed "elliptic" from the list of packages excluded from npm audit checks.

@lklimek lklimek added this to the v2.0.0 milestone Apr 25, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 25, 2025

Walkthrough

The changes update the version of the "elliptic" package from 6.5.7 to 6.6.1 across the project configuration files. This includes updating the version in the package resolution settings, runtime dependency state, and removing "elliptic" from the npm audit exclusion list. No other dependencies or configurations were modified, and there were no changes to exported or public entities.

Changes

File(s) Change Summary
.pnp.cjs, package.json Updated "elliptic" package version from 6.5.7 to 6.6.1 in dependency and resolution settings.
.yarnrc.yml Removed "elliptic" from the npmAuditExcludePackages list.

Possibly related PRs

Suggested reviewers

  • QuantumExplorer
  • shumkov

Poem

A hop and a leap, the version grows,
Elliptic now shines, as everyone knows.
No more exclusions, the audit is clean,
Our yarn is untangled, our codebase pristine.
With every small patch, we bounce to the top,
🐇✨ Upgrading together—no reason to stop!

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@lklimek lklimek changed the title build: update javascript elliptic lib build: update javascript elliptic lib to 6.6.1 Apr 25, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
package.json (1)

1-106: Suggest documenting the upgrade in the CHANGELOG

Add a CHANGELOG entry under a security or dependencies section to record the update of elliptic to 6.6.1, referencing the relevant advisory or CVE. This will improve traceability of the security fix.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b136231 and 5fe1e90.

⛔ Files ignored due to path filters (3)
  • .yarn/cache/elliptic-npm-6.6.1-87bb857cbc-dc678c9feb.zip is excluded by !**/.yarn/**, !**/*.zip
  • .yarn/cache/fsevents-patch-19706e7e35-10.zip is excluded by !**/.yarn/**, !**/*.zip
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (3)
  • .pnp.cjs (4 hunks)
  • .yarnrc.yml (0 hunks)
  • package.json (1 hunks)
💤 Files with no reviewable changes (1)
  • .yarnrc.yml
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
  • GitHub Check: Build Docker images (DAPI, dapi, dapi) / Build DAPI image
🔇 Additional comments (2)
package.json (1)

74-74:

✅ Verification successful

Approve the dependency resolution update

The elliptic package resolution has been bumped to 6.6.1 to address the security issue in earlier versions. Please verify that this version is published and free of known vulnerabilities.

Run this script to confirm:


🏁 Script executed:

#!/usr/bin/env bash
# Check that [email protected] exists on npm
npm view [email protected] version

# Audit for any remaining vulnerabilities in elliptic
npm audit --json | jq '.advisories | with_entries(select(.value.module_name=="elliptic"))'

Length of output: 531


🏁 Script executed:

#!/usr/bin/env bash
set -e
# Create a temporary project to generate a lockfile for audit
temp_dir=$(mktemp -d)
cd "$temp_dir"

npm init -y > /dev/null

# Add [email protected] and generate package-lock.json
npm install [email protected] --package-lock-only > /dev/null

# Run audit and filter only elliptic advisories
npm audit --json | jq '.advisories | with_entries(select(.value.module_name=="elliptic"))'

Length of output: 284


Approve the dependency resolution update

  • Confirmed [email protected] is published on npm.
  • npm audit reports no advisories for this version.
.pnp.cjs (1)

2614-2620:

✅ Verification successful

Approve Yarn PnP manifest updates for elliptic version bump
The elliptic dependency has been correctly upgraded to 6.6.1 in all PnP sections of the manifest. Since this file is auto-generated by Yarn, no manual adjustments are needed beyond running yarn install.
To be extra cautious, please verify that no references to the old version remain by running:

Also applies to: 6818-6824, 8279-8283, 9246-9252


🏁 Script executed:

#!/bin/bash
# Search for any remaining references to the old elliptic version
rg -n "npm:6\\.5\\.7"

Length of output: 21


Approve Yarn PnP manifest updates for elliptic version bump
I ran rg -n 'npm:6\.5\.7' across the entire .pnp.cjs and found no occurrences of the old version. Since this file is auto-generated by Yarn, no manual edits are required beyond running yarn install.

Applies to these sections as well:

  • Lines 6818–6824
  • Lines 8279–8283
  • Lines 9246–9252

@QuantumExplorer QuantumExplorer merged commit b945e47 into v2.0-dev Apr 28, 2025
18 checks passed
@QuantumExplorer QuantumExplorer deleted the deps/js-elliptic branch April 28, 2025 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants