Bitcoin BIP39: Mnemonic code for generating deterministic keys
65%
Total Score
75
100
90
90
50
No build attestation or trusted-publisher identity is present, limiting publication transparency. This is a provenance gap rather than evidence that the release is unsafe or unmaintained.
The project has a long history with 23 releases, but its latest release was over three years ago and it had no releases in the last 12 months. That weakens evidence of ongoing maintenance despite the package's maturity.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long gap since the latest release, this is the clearest sign that maintenance may be slow.
There are only eight open issues and five open pull requests, but no issues or pull requests were opened or closed in the last month. This indicates limited recent project activity.
The repository uses TypeScript, webpack, and npm build tooling, but no security scanning tools were detected. The missing scanning is a transparency gap, partly offset by the presence of build tooling and CI-related repository structure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@noble/hashes 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.