static-eval

v2.1.1

evaluate statically-analyzable expressions For more information about how to use this package see README

Latest version published 11 months ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

77 / 100

Security

No known security issues
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
2.1.1 | 01/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.5 | 03/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.2 | 02/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.1 | 09/2016
  • 0
    H
  • 0
    M
  • 0
    L
0.2.4 | 03/2015
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (3,942,035)

Download trend
GitHub Stars
175
Forks
27
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package static-eval receives a total of 3,942,035 downloads a week. As such, we scored static-eval popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package static-eval, we found that it has been starred 175 times.

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
20
Funding
No

With more than 10 contributors for the static-eval 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 static-eval is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 77/100 package health 77/100

Maintenance

Sustainable

Commit Frequency

Open Issues
11
Open PR
4
Last Release
11 months ago
Last Commit
11 months ago

Further analysis of the maintenance status of static-eval based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that static-eval demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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
11 years
Dependencies
1 Direct
Versions
20
Install Size
20.3 kB
Dist-tags
1
# of Files
12
Maintainers
39
TS Typings
Yes

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