filesaver.js-npm

v1.0.1

An HTML5 saveAs() FileSaver implementation http://eligrey.com/blog/post/saving-generated-files-on-the-client-side

MIT
Latest version published 5 years ago
    npm install filesaver.js-npm
  
We couldn't find any similar packages Browse all packages

Package Health Score

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

Popularity

Small
Download trend

Weekly Downloads (270)

Dependents
2.32K
GitHub Stars
16.77K
Forks
3.88K
Contributors
60

The npm package filesaver.js-npm receives a total of 270 downloads a week. As such, we scored filesaver.js-npm popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package filesaver.js-npm, we found that it has been starred 16,766 times, and that 2,316 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

Direct Vulnerabilities

1.0.1
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.1
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

1.0.1
  • 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 filesaver.js-npm 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 filesaver.js-npm
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
106
Open PR
18
Last Release
5 years ago
Last Commit
6 months ago

Further analysis of the maintenance status of filesaver.js-npm 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 filesaver.js-npm 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.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

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

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct
Versions
3
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

filesaver.js-npm 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.