Gathering detailed insights and metrics for npm-force-resolutions
Gathering detailed insights and metrics for npm-force-resolutions
Gathering detailed insights and metrics for npm-force-resolutions
Gathering detailed insights and metrics for npm-force-resolutions
npm-update-resolutions
node package to update resolutions automatically after generating the npm audit json file.
@flina/common-page
``` "scripts": { "preinstall": "npx npm-force-resolutions" } ``` > Use it after the `package-lock.json` was generated. [npm-force-resolutions](https://github.com/rogeriochaves/npm-force-resolutions) ``` npm install example-package-name --no-audit ``` [h
Force npm to install a specific transitive dependency version
npm install npm-force-resolutions
Typescript
Module System
Node Version
NPM Version
98.7
Supply Chain
87.2
Quality
75.3
Maintenance
100
Vulnerability
99.6
License
Clojure (100%)
Total Downloads
49,618,216
Last Day
6,693
Last Week
159,557
Last Month
702,958
Last Year
8,447,708
570 Stars
46 Commits
27 Forks
6 Watchers
11 Branches
2 Contributors
Updated on Mar 21, 2025
Minified
Minified + Gzipped
Latest Version
0.0.10
Package Id
npm-force-resolutions@0.0.10
Size
2.32 MB
NPM Version
6.14.9
Node Version
14.15.3
Published on
Feb 26, 2021
Cumulative downloads
Total Downloads
Last Day
28.6%
6,693
Compared to previous day
Last Week
-6.9%
159,557
Compared to previous week
Last Month
-5.1%
702,958
Compared to previous month
Last Year
-8.2%
8,447,708
Compared to previous year
3
This packages modifies package-lock.json to force the installation of specific version of a transitive dependency (dependency of dependency), similar to yarn's selective dependency resolutions, but without having to migrate to yarn.
The use case for this is when there is a security vulnerability and you MUST update a nested dependency otherwise your project would be vulnerable. But this should only be used as a last resource, you should first update your top-level dependencies and file an issue for them to update the vulnerable sub-dependencies (npm ls <vulnerable dependency>
can help you with that).
First add a field resolutions
with the dependency version you want to fix to your package.json
, for example:
1"resolutions": { 2 "hoek": "4.2.1" 3}
Then add npm-force-resolutions to the preinstall script so that it patches the package-lock
file before every npm install
you run:
1"scripts": { 2 "preinstall": "npx npm-force-resolutions" 3}
Now just run npm install
as you would normally do:
npm install
To confirm that the right version was installed, use:
npm ls hoek
If your package-lock changes, you may need to run the steps above again.
To build the project from source you'll need to install clojure. Then you can run:
npm install
npm run build
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/26 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
license file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
52 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-16
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More