chore: resolve NPM audit warnings

[shumkov]

Issue being fixed or feature implemented

├─ level-concat-iterator
│  ├─ ID: level-concat-iterator (deprecation)
│  ├─ Issue: Superseded by abstract-level (https://github.com/Level/community#faq)
│  ├─ Severity: moderate
│  ├─ Vulnerable Versions: 2.0.1
│  │ 
│  ├─ Tree Versions
│  │  └─ 2.0.1
│  │ 
│  └─ Dependents
│     └─ abstract-leveldown@npm:6.2.3
│
├─ level-errors
│  ├─ ID: level-errors (deprecation)
│  ├─ Issue: Superseded by abstract-level (https://github.com/Level/community#faq)
│  ├─ Severity: moderate
│  ├─ Vulnerable Versions: 2.0.1
│  │ 
│  ├─ Tree Versions
│  │  └─ 2.0.1
│  │ 
│  └─ Dependents
│     └─ levelup@npm:4.4.0
│
└─ systeminformation
   ├─ ID: 1101384
   ├─ Issue: Systeminformation has command injection vulnerability in getWindowsIEEE8021x (SSID)
   ├─ URL: https://github.com/advisories/GHSA-cvv5-9h9w-qp2m
   ├─ Severity: high
   ├─ Vulnerable Versions: <=5.23.6
   │ 
   ├─ Tree Versions
   │  └─ 5.22.11
   │ 
   └─ Dependents
      └─ dashmate@workspace:packages/dashmate

What was done?

• Updated systeminformation in dashmate
• Added to the ignore list deprecated leveldb-related packages

How Has This Been Tested?

yarn npm audit --environment production --all --recursive

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

• Dependencies
  • Updated systeminformation package from version 5.22.11 to 5.25.11 across multiple configuration files
• Configuration
  • Added level-errors and level-concat-iterator to npm audit exclusion list

[coderabbitai]

Walkthrough

This pull request involves updates to package dependencies and configurations across multiple files. The primary change is upgrading the systeminformation package from version 5.22.11 to 5.25.11 in the .pnp.cjs file and packages/dashmate/package.json. Additionally, the .yarnrc.yml file has been modified to exclude two new packages (level-errors and level-concat-iterator) from npm audit checks.

Changes

File	Change Summary
.pnp.cjs	Updated systeminformation package version from npm:5.22.11 to npm:5.25.11 in dependencies and package information
.yarnrc.yml	Added level-errors and level-concat-iterator to npmAuditExcludePackages
packages/dashmate/package.json	Updated systeminformation dependency from ^5.22.11 to ^5.25.11

Possibly related PRs

• chore: address vulnerabilty GHSA-mwcw-c2x4-8c55 #2382: Updates nanoid package version in .pnp.cjs
• chore(dashmate)!: update Core to version 22 #2384: Modifies .pnp.cjs with Docker image version update
• chore(dashmate): set tenderdash version to 1 #2385: Updates Docker image version in configuration files

Suggested reviewers

• QuantumExplorer
• lklimek

Poem

🐰 Hop, hop, version update time!
Systeminformation's new design
Dependencies dancing with glee
From 5.22 to 5.25, can't you see?
A package upgrade, smooth and fine! 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a809df7 and 0cda9b9.

⛔ Files ignored due to path filters (3)

• .yarn/cache/systeminformation-npm-5.22.11-e704a1605b-315cd3f2cc.zip is excluded by !**/.yarn/**, !**/*.zip
• .yarn/cache/systeminformation-npm-5.25.11-e1c9348b68-9a43bb8991.zip is excluded by !**/.yarn/**, !**/*.zip
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (3)

• .pnp.cjs (2 hunks)
• .yarnrc.yml (1 hunks)
• packages/dashmate/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .pnp.cjs

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Build Docker images (DAPI, dapi, dapi) / Build DAPI image
• GitHub Check: Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
• GitHub Check: Build JS packages / Build JS

🔇 Additional comments (2)

.yarnrc.yml (1)

24-25: LGTM! Consider tracking the leveldb update.

The additions align with the existing pattern of excluding deprecated leveldb packages. This is an acceptable temporary solution while planning the larger leveldb update.

Let's track all the leveldb-related TODOs to ensure they're addressed comprehensively:

✅ Verification successful

Verified: The leveldb update needs comprehensive planning

Found 7 interconnected leveldb packages in the dependency tree, all requiring updates. The audit exclusions are appropriate as a temporary measure.

• All excluded packages are either direct or transitive dependencies through [email protected]
• The consistent TODO comments correctly identify the scope of the required update

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: List all leveldb-related TODOs to track the scope of required updates

echo "Checking for leveldb-related TODOs in .yarnrc.yml:"
rg "TODO: Update leveldb" .yarnrc.yml

Length of output: 401

---

Script:

#!/bin/bash
# Check for any other leveldb-related packages in dependencies
echo "Checking for leveldb-related packages in package.json:"
rg "level[^a-z]" package.json

# Look for any migration discussions or plans
echo -e "\nChecking for leveldb migration discussions:"
fd "MIGRATION|UPGRADE|README" --type f --exec rg -l "leveldb|abstract-level" {} \;

Length of output: 341

---

Script:

#!/bin/bash
# Check for leveldb-related packages in all dependency files
echo "Checking package dependencies:"
fd "package.json|package-lock.json|yarn.lock" --type f --exec rg "level-|leveldb|levelup|leveldown" {} \;

Length of output: 1210

packages/dashmate/package.json (1)

94-94: LGTM! Version update addresses security vulnerability.

The update to systeminformation ^5.25.11 fixes the high severity command injection vulnerability (versions <=5.23.6 were vulnerable).

Let's verify this is the only instance of systeminformation that needs updating:

✅ Verification successful

✅ Verified: systeminformation is properly updated

The security update is complete. Only one instance of systeminformation exists (in packages/dashmate/package.json) and it's already using the secure version ^5.25.11.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any other instances of systeminformation dependency

echo "Checking for systeminformation dependencies across all package.json files:"
rg '"systeminformation":\s*"\^?5\.(?:22|23|21|20|19|18|17|16|15|14|13|12|11|10|[0-9])\.' -g 'package.json'

Length of output: 265

---

Script:

#!/bin/bash
# Search for any systeminformation dependency with surrounding context
echo "Searching for all systeminformation dependencies:"
rg '"systeminformation"' -g 'package.json' -C 3

Length of output: 546

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.