0m

v1.0.0

fanshichao QQ:1829106

MIT
Latest version published 2 years ago
    npm install 0m
  

Package Health Score

47 / 100

Security

Security review needed
Powered by Snyk
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
1.0.0 | 10/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test 0m
Get started free

Popularity

Small

Weekly Downloads (3)

Download trend
Dependents
0
GitHub Stars
17.4K
Forks
3.23K
Contributors
440

Direct Usage Popularity


The npm package 0m receives a total of 3 downloads a week. As such, we scored 0m popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package 0m, we found that it has been starred 17,403 times, and that 0 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

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
440
Funding
No

A good and healthy external contribution signal for 0m project, which invites more than one hundred open source maintainers to collaborate on the repository.

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


Embed Package Health Score Badge

package health: 47/100 package health 47/100

Maintenance

Inactive
archived

Commit Frequency

No Recent Commits
Open Issues
2.17K
Open PR
0
Last Release
2 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of 0m 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 0m 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.

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
1 Direct
Versions
2
Install Size
478 B
Dist-tags
1
# of Files
2
Maintainers
1
TS Typings
Yes

0m 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.