101

v1.6.3

common javascript utils that can be required selectively that assume es5+

MIT
Latest version published 3 years ago
    npm install 101
  

Package Health Score

32 / 100

Popularity

Popular

Weekly Downloads (131,290)

Download trend
Dependents
105
GitHub Stars
1.56K
Forks
83
Contributors
20

Direct Usage Popularity

Occasionally

The npm package 101 receives a total of 131,290 downloads a week. As such, we scored 101 popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package 101, we found that it has been starred 1,560 times, and that 105 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 issues found
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

05/2015
05/2015
05/2015
03/2016
04/2018

Direct Vulnerabilities

0.17.0
0.18.0
0.19.0
1.5.0
Popular
1.6.3

Indirect Vulnerabilities

0.17.0
0.18.0
0.19.0
1.5.0
Popular
1.6.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.17.0
  • 0
    H
  • 0
    M
  • 0
    L
0.18.0
  • 0
    H
  • 0
    M
  • 0
    L
0.19.0
  • 0
    H
  • 0
    M
  • 0
    L
1.5.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.6.3
  • 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 101 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 101
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
21
Open PR
2
Last Release
3 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of 101 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 101 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

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

With more than 10 contributors for the 101 repository, this is possibly a sign for a growing and inviting community.

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


Embed Package Health Score Badge

package health: 32/100 package health 32/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
3 Direct
Versions
44
Install Size
59.1 kB
Dist-tags
1
# of Files
50
Maintainers
1
TS Typings
No

101 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.