adds node crypto signing for browsers
72%
Total Score
75
50
100
50
Nine runtime dependencies create meaningful supply-chain surface area for a cryptographic browser package, though the signal does not show an abnormal or excessive dependency profile by itself.
One contributor made 100% of the last three months' commits. Organizational ownership provides some handoff capacity, but no second active contributor is shown.
The repository had 3 commits in the last 3 months, showing current activity, but the volume is modest and all activity is concentrated in one contributor.
The repository has no security policy, leaving reporting and response expectations undocumented for a security-sensitive package.
All six workflows were analyzed with no audit findings and no untrusted checkout or script-injection paths. However, all six action references are unpinned, which weakens build reproducibility and action supply-chain control.
| Title | Versions | Severity |
|---|---|---|
CVE-2023-46234 browserify-sign is vulnerable to Improper Verification of Cryptographic Signature in versions 2.6.0 - 4.2.1. | 2.6.0 - 4.2.1 | High |
| Dependency | Last Release | Score |
|---|---|---|
bn.js Version ^5.2.3 | — | — |
elliptic Version ^6.6.1 | — | — |
inherits Version ^2.0.4 | — | — |
parse-asn1 Version ^5.1.9 | — | — |
create-hash Version ^1.2.0 | — | — |
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.