@fredfogerty/np

v2.9.0

A better `npm publish` For more information about how to use this package see README

Latest version published 6 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

55 / 100

Security

Security review needed
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
2.9.0 | 10/2016
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (2)

Download trend
Dependents
7.05K
GitHub Stars
6.79K
Forks
325
Contributors
80

Direct Usage Popularity


The npm package @fredfogerty/np receives a total of 2 downloads a week. As such, we scored @fredfogerty/np popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @fredfogerty/np, we found that it has been starred 6,787 times, and that 7,050 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active
Readme.md
Yes
Contributing.md
No
Code of Conduct
Yes
Contributors
80
Funding
Yes

With more than 10 contributors for the @fredfogerty/np repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 55/100 package health 55/100

Maintenance

Inactive

Commit Frequency

Open Issues
102
Open PR
0
Last Release
6 years ago
Last Commit
3 months ago

Further analysis of the maintenance status of @fredfogerty/np based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @fredfogerty/np is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=4

Age
6 years
Dependencies
12 Direct
Versions
2
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

@fredfogerty/np has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.