browser-pack

v6.1.0

pack node-style source files from a json stream into a browser bundle 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

74 / 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
6.1.0 | 03/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.0.4 | 02/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.1 | 05/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.4 | 05/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.2.0 | 10/2014
  • 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

Influential project

Weekly Downloads (1,305,854)

Download trend
GitHub Stars
174
Forks
58
Contributors
20

Direct Usage Popularity

TOP 5%

The npm package browser-pack receives a total of 1,305,854 downloads a week. As such, we scored browser-pack popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package browser-pack, we found that it has been starred 174 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
20
Funding
No

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


Embed Package Health Score Badge

package health: 74/100 package health 74/100

Maintenance

Sustainable

Commit Frequency

No Recent Commits
Open Issues
5
Open PR
10
Last Release
7 years ago
Last Commit
4 years ago

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

Package

Node.js Compatibility
not defined

Age
12 years
Dependencies
6 Direct
Versions
46
Install Size
30 kB
Dist-tags
1
# of Files
25
Maintainers
39
TS Typings
Yes

browser-pack 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.