Compute ripemd160 of bytes or strings.
68%
Total Score
75
100
94
50
A prepack script runs during packaging. This is not inherently unsafe, but it adds a build step that should be understood when reproducing releases.
There were no commits and no active maintainers in the last three months. Although a release was published during the broader 12-month period, the recent source inactivity is a maintenance concern.
The repository reports no build tooling and no security scanning tools. For a small pure-JavaScript package this is not disqualifying, but it reduces automated assurance.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is partly offset by the package's small scope and mature source repository.
All six analyzed action references are unpinned, which is a workflow hygiene concern. The two pull_request_target workflows have no untrusted checkouts or script-injection findings, and no high- or medium-severity audit findings were reported.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
inherits Version ^2.0.4 | — | — |
hash-base Version ^3.1.2 | — | — |
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.