safer-eval

v1.3.6

harmful as eval

MIT
Latest version published 2 years ago
    npm install safer-eval
  

Package Health Score

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

Popularity

Recognized

Weekly Downloads (21,351)

Download trend
Dependents
25
GitHub Stars
19
Forks
18
Contributors
3

Direct Usage Popularity

Occasionally

The npm package safer-eval receives a total of 21,351 downloads a week. As such, we scored safer-eval popularity level to be Recognized.

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

02/2017
03/2017
01/2018
12/2019

Direct Vulnerabilities

1.0.1
1.1.0
1.2.3
Popular
1.3.6

Indirect Vulnerabilities

1.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.3.6
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0
  • 0
    H
  • 0
    M
  • 0
    L
1.2.3
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.3.6
  • 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 safer-eval 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 safer-eval
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
5
Open PR
0
Last Release
2 years ago
Last Commit
12 months ago

Further analysis of the maintenance status of safer-eval 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 safer-eval 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
No
Code of Conduct
No
Contributors
3
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 29/100 package health 29/100

Package

Node.js Compatibility
>=6.0.0

Age
4 years
Dependencies
1 Direct
Versions
15
Install Size
54.5 kB
Dist-tags
1
# of Files
10
Maintainers
1
TS Typings
No

safer-eval 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.