npmpackage.info

Gathering detailed insights and metrics for nyarn

Approximately 800 new packages are uploaded to the npm registry every day. This number can vary, but it reflects the active and growing nature of the JavaScript development community.

nyarn

A shell alias that prevent developers from mistakenly installing packages. (npm <=> yarn <=> lerna)

1.2.0

MIT

Shell

2,838

Installations

npm install nyarn

Score

47.8

Supply Chain

77.7

Quality

75.1

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

View all 1 contributors

Developer

matzkoh

Module System

BETA

N/A

Unable to determine the module system for this package.

Statistics

3 Stars

8 Commits

2 Watching

1 Branches

1 Contributors

Updated on 28 Jan 2022

Languages

Shell (100%)

Total Downloads

Cumulative downloads

Total Downloads

2,838

Last day

Compared to previous day

Last week

Compared to previous week

Last month

-24%

Compared to previous month

Last year

39.9%

670

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

nyarn

Installation

Global install from npm.

$ npm i -g nyarn

Add lines to your shell configuration file.

1alias npm='nyarn npm'
2alias yarn='nyarn yarn'
3# or
4# alias yarnpkg='nyarn yarnpkg'

Example

$ npm init -y
$ npm i

$ ls -1
package-lock.json
package.json

$ yarn
There is a lockfile in this project generated by npm.
You should use npm instead of yarn.

$ yarn init -y
$ yarn

$ ls -1
node_modules
package.json
yarn.lock

$ npm i
There is a lockfile in this project generated by yarn.
You should use yarn instead of npm.

$ lerna init

$ ls -1
lerna.json
package.json
packages

$ npm i
This is a root package of Lerna.
You should use lerna instead of npm.

$ cd packages
$ npm i
This is a Lerna scoped package.
You should use lerna instead of npm.

Question

Q. My project use yarn, but I just want to run npm -v anyway.

A. command npm -v

No vulnerabilities found.

10

License

Determines if the project has defined a license.

10

Binary-Artifacts

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

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

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

CII-Best-Practices

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

0

SAST

Determines if the project uses static code analysis.

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

Security-Policy

Determines if the project has published a security policy.

Score

3

/10

Last Scanned on 2024-11-11

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