fstream

v1.0.12

Advanced file system stream things

ISC
Latest version published 2 years ago
    npm install fstream
  

Explore Similar Packages

Package Health Score

72 / 100
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Influential project

Weekly Downloads (6,107,480)

Dependents
726
GitHub Stars
204
Forks
52
Contributors
20

The npm package fstream receives a total of 6,107,480 downloads a week. As such, we scored fstream popularity level to be Influential project.

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

0.0.1
0.1.31
1.0.12
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.1
0.1.31
1.0.12
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.1
0.1.31
1.0.12
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
ISC

Security Policy
No

We found a way for you to contribute to the project! Looks like fstream 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 fstream
Keep your project free of vulnerabilities with Snyk

Maintenance

Sustainable

Commit Frequency

No Recent Commits
Open Issues
26
Open PR
9
Last Release
2 years ago
Last Commit
2 years ago

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

An important project maintenance signal to consider for fstream 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
No
Contributors
20
Funding
No

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


Embed Package Health Score Badge

package health: 72/100 package health 72/100

Package

Node.js Compatibility
>=0.6

Age
9 years
Dependencies
4 Direct
Versions
47
Install Size
63.5 kB
Dist-tags
1
# of Files
23
Maintainers
6
TS Typings
No

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