Orange-OpenSource / Orange-OpenSource/github-security-alerts

When I install NPM dependencies on `macOS`, I get a lot of NPM warnings about deprecated dependencies

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5
Forks
1
Avg merge
9h 26m
Merged PRs (30d)
13

Description

Description

As a developer,
When I follow the DEVELOP file to build the project and run npm install,
I get several NPM warnings about deprecated dependencies
And several warnings about dependencies with vulnerabilities

Details

Command:

npm install

Logs:

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated whatwg-encoding@3.1.1: Use @exodus/bytes instead for a more spec-conformant and faster implementation
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead
npm warn deprecated @xmldom/xmldom@0.7.13: this version has critical issues, please update to the latest version
npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm warn deprecated glob@11.1.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

added 969 packages, and audited 970 packages in 1m

222 packages are looking for funding
  run `npm fund` for details

7 vulnerabilities (3 moderate, 4 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

Suggestion

  • Replace inflight@1.0.6
  • Upgrade rmraf to v4
  • Upgrade glob
  • Replace whatwg-encoding
  • Update @xmldom/xmldom

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by following the DEVELOP file and running npm install on macOS to reproduce the warnings. Inspect the dependency tree and use npm audit to identify which listed packages require direct or transitive updates. Done means the deprecated-dependency warnings and reported vulnerabilities are addressed without breaking the build.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.