browser-builtins

v3.3.1

Builtins that were extracted from node-browser-resolve on which browserify depends For more information about how to use this package see README

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

46 / 100

Explore Similar Packages

Security

Security review needed
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
3.3.1 | 09/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.2.0 | 07/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.5 | 10/2013
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.7 | 08/2013
Popular
  • 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

Limited

Weekly Downloads (507)

Download trend
GitHub Stars
62
Forks
30
Contributors
20

Direct Usage Popularity

Occasionally

The npm package browser-builtins receives a total of 507 downloads a week. As such, we scored browser-builtins popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package browser-builtins, we found that it has been starred 62 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-builtins 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-builtins is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 46/100 package health 46/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
1
Last Release
9 years ago
Last Commit
8 years ago

Further analysis of the maintenance status of browser-builtins 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 browser-builtins 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
11 years
Dependencies
17 Direct
Versions
19
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
2
TS Typings
No

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