package.json

v2.0.1

Get the package.json content either from npm or from a git repository.

MIT
Latest version published 5 years ago
    npm install package.json
  

Package Health Score

44 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Recognized

Weekly Downloads (17,262)

Dependents
3
GitHub Stars
4
Forks
5
Contributors
1

The npm package package.json receives a total of 17,262 downloads a week. As such, we scored package.json popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package package.json, we found that it has been starred 4 times, and that 3 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.0
1.0.2
2.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.0
1.0.2
2.0.1
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.0
1.0.2
2.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like package.json is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test package.json
Fix it in your project with Snyk!

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
0
Last Release
5 years ago
Last Commit
9 months ago

Further analysis of the maintenance status of package.json 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 package.json 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

Limited
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
1
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like package.json is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 44/100 package health 44/100

Package

Node.js Compatibility
not defined

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

package.json 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.