npmpackage.info

Gathering detailed insights and metrics for npm-link-check

Other packages similar to npm-link-check

check-error

2.1.1

Error comparison and information related utility for node and the browser

npm-install-checks

7.1.1

Check the engines and platform fields in package.json

path-type

6.0.0

Check if a path is a file, directory, or symlink

type-check

0.4.0

type-check allows you to check the types of JavaScript values at runtime with a Haskell like type syntax.

Gathering detailed insights and metrics for npm-link-check

npm-link-check

🏁 CLI utility that checks whether a project's current node modules tree contains npm-link'ed packages

5.0.1

MIT

JavaScript

10.46 kB

220,590 3.2

Installations

npm install npm-link-check

Score

64.3

Supply Chain

Quality

79.5

Maintenance

100

Vulnerability

99.6

License

Pull Requests

Open

1

Total

49

Closed

15

Merged

33

Issues

Open

0

Total

2

Closed

2

Releases

v5.0.1

Published on 01 May 2024

v5.0.0

Published on 17 Jan 2023

v4.0.0

Published on 16 Jul 2020

View all 3 releases

Contributors

View all 5 contributors

Developer

etpinard

Developer Guide

BETA

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

Bundle Size

31.26 kB

Minified

10.46 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

220,590

Last day

2.4%

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

Dependencies

glob

Dev Dependencies

assert coveralls fs-extra is-plain-object mocha nyc snazzy standard

Versions

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.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

6

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

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 More