Gathering detailed insights and metrics for npmvet
Gathering detailed insights and metrics for npmvet
Gathering detailed insights and metrics for npmvet
Gathering detailed insights and metrics for npmvet
npm install npmvet
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
205 Stars
85 Commits
10 Forks
8 Watching
3 Branches
5 Contributors
Updated on 30 Apr 2024
Minified
Minified + Gzipped
TypeScript (68.48%)
JavaScript (31.52%)
Cumulative downloads
Total Downloads
Last day
4.2%
123
Compared to previous day
Last week
53%
693
Compared to previous week
Last month
1.9%
2,305
Compared to previous month
Last year
-25.3%
31,265
Compared to previous year
6
NPM Vet is a simple CLI tool to help vet your npm package versions. NPM Vet can be used locally, or as a CI build-step to prevent builds passing with mismatched package versions. To read more about NPM Vet, visit the Hark website.
$ npm install npmvet -g
Usage: npmvet [options]
Options:
-h, --help output usage information
-V, --version output the version number
-p, --package <package> package.json file location (Default: .)
-m, --modules <modules> node_modules folder location (Default: .)
-r, --renderer <renderer> Renderer to use (Default: inlinetable)
-s, --strict Using the CI renderer, fail build if any packages unlocked (Default: false, flag)
If you're using the CI renderer (see below) the -s
flag will enable strict mode. In which builds will fail if versions are unlocked, not just unmatching.
Renderers are used to dictate how to output the data NPM Vet collects. The default is inlinetable
.
$ npmvet -r inlinetable
The default renderer, inlinetable
will print a table inline with your current process. You can use this locally to visualise package differences.
$ npmvet -r ci
To prevent your CI builds passing with mismatched package versions, use the CI renderer. If any package version mismatches are found, the build will fail:
Or if there are no mismatching package versions, your build will continue (and hopefully pass!):
The blessed
renderer will render a table inside a screen, that has be exited by the user to escape.
$ npmvet -r blessed
The JSON
renderer will print a JSON array with match information for each package.
$ npmvet -r json
1[ 2 { 3 "name": "blessed", 4 "packageVersion": "0.1.81", 5 "installedVersion": "0.1.81", 6 "matches": true, 7 "locked": false 8 }, 9 { 10 "name": "chalk", 11 "packageVersion": "1.1.3", 12 "installedVersion": "1.1.3", 13 "matches": true, 14 "locked": false 15 }, 16 { 17 "name": "jest", 18 "packageVersion": "18.1.0", 19 "installedVersion": "18.1.0", 20 "matches": true, 21 "locked": false 22 } 23]
For information regarding contributing to this project, please read the Contributing document.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 5/11 approved changesets -- score normalized to 4
Reason
6 existing vulnerabilities detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy 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
Score
Last Scanned on 2024-11-25
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