RSA for browserify
68%
Total Score
75
100
86
67
50
No build attestation or trusted-publisher configuration is present. This weakens release transparency, although it does not by itself indicate that the release is unsafe.
The package defines prepack and prepublish lifecycle scripts. These are not necessarily unsafe, but they add build-time behavior that should be understood when reproducing or republishing the package.
The package has 11 releases since December 2014, but none in the last 12 months and the latest release was about two years ago. This suggests slowing maintenance, though the long history provides some maturity.
The repository had zero commits and zero active maintainers in the last three months. Combined with no registry release in the last year, this raises ongoing maintenance risk.
No build tools or security-scanning tools were detected. For a small package this is not severe, but it leaves less evidence of automated maintenance and security checks.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
bn.js Version ^5.2.1 | — | — |
randombytes Version ^2.1.0 | — | — |
safe-buffer Version ^5.2.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.