browserfs

v1.4.3

A filesystem in your browser! For more information about how to use this package see README

Latest version published 7 years 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

53 / 100

Explore Similar Packages

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
1.4.3 | 08/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.0 | 03/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.6.1 | 09/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.5.13 | 08/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.6 | 10/2015
  • 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

Recognized

Weekly Downloads (5,682)

Download trend
GitHub Stars
3.08K
Forks
221
Contributors
-

Direct Usage Popularity

TOP 10%

The npm package browserfs receives a total of 5,682 downloads a week. As such, we scored browserfs popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package browserfs, we found that it has been starred 3,084 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
0
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive

Commit Frequency

Open Issues
31
Open PR
0
Last Release
7 years ago
Last Commit
6 months ago

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

Package

Node.js Compatibility
>= 0.10

Age
10 years
Dependencies
2 Direct
Versions
33
Install Size
0 B
Dist-tags
2
# of Files
0
Maintainers
1
TS Typings
Yes

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