browserify

v17.0.0

browser-side require() the node way For more information about how to use this package see README

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

83 / 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
17.0.0 | 10/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
16.5.2 | 08/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
15.2.0 | 01/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
14.5.0 | 10/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
14.4.0 | 05/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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

Key ecosystem project

Weekly Downloads (1,976,880)

Download trend
GitHub Stars
14.39K
Forks
1.25K
Contributors
180

Direct Usage Popularity

TOP 5%

The npm package browserify receives a total of 1,976,880 downloads a week. As such, we scored browserify popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package browserify, we found that it has been starred 14,390 times.

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

Community

Active
Readme.md
Yes
Contributing.md
No
Code of Conduct
Yes
Contributors
180
Funding
Yes

A good and healthy external contribution signal for browserify project, which invites more than one hundred open source maintainers to collaborate on the repository.


Embed Package Health Score Badge

package health: 83/100 package health 83/100

Maintenance

Sustainable

Commit Frequency

No Recent Commits
Open Issues
358
Open PR
32
Last Release
3 years ago
Last Commit
1 year ago

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

Age
12 years
Dependencies
48 Direct
Versions
485
Install Size
361 kB
Dist-tags
1
# of Files
431
Maintainers
40
TS Typings
Yes

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