The source project has no tests, security policy, security scanning, or automated workflows, which is a serious transparency gap for a cryptography library. Its Unlicense and lack of install-time scripts are positive, but they do not offset the maintenance concerns.
38%
Total Score
0
63
75
The package has had four releases, but none in the last 12 months and the latest release was about 2 years and 2 months ago, indicating abandonment risk.
There were zero commits and zero active maintainers in the last 3 months, reinforcing the long period without visible maintenance.
The artifact has no README or tests, while the exact version has GitHub release notes. The missing consumer documentation and tests are concerning for a cryptography library, although release notes provide some transparency.
The repository name does not match the package name, and no README package mention was collected. This raises concern that the linked repository may not clearly establish ownership of this package.
The project uses Composer, but no security scanning tools are present. For a library handling cryptographic operations, that weakens maintenance and security-process transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
paragonie/ecc Version ^2.0.0 | — | — |
bitwasp/bech32 Version ^0.0.1 | — | — |
composer/semver Version ^1.4.0|^3.2.0 | — | — |
bitwasp/buffertools Version ^0.5.0 | — | — |
lastguest/murmurhash Version ^2.0.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.