Installations
npm install npm-link-checkScore
64.3
Supply Chain
88
Quality
79.5
Maintenance
100
Vulnerability
99.6
License
Releases
Contributors
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?v=4){kind=avatar}
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4){kind=avatar}
Developer
etpinard
Developer Guide
Module System
CommonJS
Min. Node Version
Typescript Support
No
Node Version
20.11.1
NPM Version
10.7.0
Statistics
22 Stars
154 Commits
1 Forks
2 Watching
2 Branches
5 Contributors
Updated on 01 May 2024
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
220,590
Last day
2.4%
85
Compared to previous day
Last week
-11.6%
459
Compared to previous week
Last month
-16.8%
2,039
Compared to previous month
Last year
52%
27,602
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
npm-link-check
CLI utility that checks whether a project's current node modules tree contains npm-link'ed packages.
So that you don't build a distributed bundle containing linked packages ever again!
npm-link-check even works with npm scoped packages. Big ups @Istenes for that PR :beers:
Install
1# for CLI use: 2npm install -g npm-link-check 3 4# for npm-script use: 5npm install npm-link-check
Usage
CLI
1# to check current working directory 2npm-link-check 3 4# to check arbitrary project 5npm-link-check path/to/project/root
npm-link-check will log something like:
Some npm-link\'ed packaged were found:
- package dummy (at node_modules/dummy) is linked
and exit with code 1 if one or many packages npm-link'ed are found. Big ups to @c-eliasson for cleaning that up!
As a pre-version check
In this era of bundled and transpiled javascript, it is common for projects to
build a distributed version when running the npm version task. Using npm-link-check, the
often neglected check for npm-link'ed packages can automated as follow:
In your project's package.json, add:
1{ 2 "scripts": { 3 "preversion": "npm-link-check" 4 } 5}
making npm-link-check run on npm version before your package's version is
bumped. If an npm-link'ed package if found, the npm version task will be
aborted.
Credits
2024 Étienne Tétreault-Pinard. MIT License
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
4 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/etpinard/npm-link-check/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/etpinard/npm-link-check/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/coveralls.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/etpinard/npm-link-check/coveralls.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/coveralls.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/etpinard/npm-link-check/coveralls.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/coveralls.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/etpinard/npm-link-check/coveralls.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/ci.yml:26
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 1 out of 2 npmCommand dependencies pinned
Reason
Found 0/7 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Warn: no topLevel permission defined: .github/workflows/coveralls.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 27 are checked with a SAST tool
Score
3.2
/10
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 MoreOther packages similar to npm-link-check
check-error
Error comparison and information related utility for node and the browser
npm-install-checks
Check the engines and platform fields in package.json
path-type
Check if a path is a file, directory, or symlink
type-check
type-check allows you to check the types of JavaScript values at runtime with a Haskell like type syntax.