supervillains

v3.0.0

Get supervillain names

MIT
Latest version published 3 years ago
    npm install supervillains
  

Package Health Score

48 / 100

Popularity

Limited

Weekly Downloads (851)

Download trend
Dependents
8
GitHub Stars
101
Forks
17
Contributors
6

Direct Usage Popularity

Uncommon

The npm package supervillains receives a total of 851 downloads a week. As such, we scored supervillains popularity level to be Limited.

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

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

05/2015
02/2019
05/2019

Direct Vulnerabilities

1.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.0
2.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

1.0.0
  • 0
    H
  • 0
    M
  • 0
    L
2.2.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
3.0.0
  • 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 supervillains 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 supervillains
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
3 years ago
Last Commit
11 months ago

Further analysis of the maintenance status of supervillains 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 supervillains 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
Yes
Contributors
6
Funding
Yes

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Package

Node.js Compatibility
>=8

Age
7 years
Dependencies
1 Direct
Versions
6
Install Size
14.7 kB
Dist-tags
1
# of Files
6
Maintainers
1
TS Typings
No

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