Alert
Unable to verify the project's public source code repository.
  1. Advisor
  2. JavaScript packages
  3. finally-polyfill

finally-polyfill

v0.2.0

Latest version published 5 years ago
License: MIT
NPM

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

42 / 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
0.2.0 | 01/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.0 | 01/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.

Get started free

Popularity

Small

Weekly Downloads (2,646)

Download trend
GitHub Stars
?
Forks
?
Contributors
-

Direct Usage Popularity

Occasionally

The npm package finally-polyfill receives a total of 2,646 downloads a week. As such, we scored finally-polyfill popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package finally-polyfill, we found that it has been starred ? times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
0
Funding
No

This project has seen only 10 or less contributors.

Embed Package Health Score Badge

package health: 42/100 package health 42/100

Maintenance

Inactive

Commit Frequency

Unavailable commit data
Open Issues
?
Open PR
?
Last Release
5 years ago
Last Commit
unknown

Further analysis of the maintenance status of finally-polyfill 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 finally-polyfill 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.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
5 years
Dependencies
0 Direct
Versions
3
Install Size
1.47 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

finally-polyfill 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.