@types/browserify

v12.0.40

TypeScript definitions for browserify For more information about how to use this package see README

Latest version published 1 year 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

61 / 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
12.0.40 | 11/2023
Popular
  • 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

Popular

Weekly Downloads (20,379)

Download trend
GitHub Stars
48.45K
Forks
30.14K
Contributors
-

Direct Usage Popularity

TOP 30%

The npm package @types/browserify receives a total of 20,379 downloads a week. As such, we scored @types/browserify popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @types/browserify, we found that it has been starred 48,455 times.

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

Community

Limited
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 @types/browserify is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 61/100 package health 61/100

Maintenance

Inactive

Commit Frequency

Open Issues
549
Open PR
195
Last Release
1 year ago
Last Commit
2 months ago

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

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
9 years
Dependencies
2 Direct
Versions
22
Install Size
13.8 kB
Dist-tags
40
# of Files
5
Maintainers
1
TS Typings
No

@types/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.