Homepage

crypto-browserify vulnerabilities

implementation of crypto for the browser
Licenses: MIT
Published: 13 years ago Last updated: 1 years ago Latest version: 3.12.1 Latest non-vulnerable version: 3.12.1
npm
GitHub

Package Health Score

71/100
  • securitySecurity review needed
  • popularityInfluential project
  • maintenanceSustainable
  • communitySustainable

Maintenance

SUSTAINABLE

Commit Frequency

No commits over the last 6 months

Open Issues
34
Open PR
4
New PRS
1
Last Release
1 years ago
Last Commit
1 years ago
Maintainers
5

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

Popularity

INFLUENTIAL PROJECT
Weekly downloads (9.4M)
GitHub Stars
683
Forks
208
Contributors
30

The npm package crypto-browserify receives a total of 9,396,106 downloads a week. As such, we scored crypto-browserify popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package crypto-browserify, we found that it has been starred 683 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
30
Funding
Yes
LICENSE
MIT

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

License

MIT>=0;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the crypto-browserify package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Security

SECURITY REVIEW NEEDED
Show only direct vulnerabilities in latest version

No vulnerabilities found in the latest version

There are 1 total vulnerabilities, but none affect the latest version (3.12.1)

No vulnerabilities found

Package versions

76 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
3.12.122 Oct, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.12.03 Nov, 2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.11.111 Jul, 2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.11.03 Nov, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.10.027 Sep, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.9.1416 Apr, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.9.1323 Feb, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.9.122 Feb, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.9.1129 Jan, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.9.1026 Jan, 2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

crypto-browserify dependencies

12 IN TOTAL
browserify-cipherbrowserify-signcreate-ecdhcreate-hashcreate-hmacdiffie-hellmanhash-baseinheritspbkdf2public-encryptrandombytesrandomfill

crypto-browserify development dependencies

9 IN TOTAL
@ljharb/eslint-configeslinthash-test-vectorsnycobject.entriespseudorandombytessafe-buffersemvertape