isakura/blockchain
The MIT declaration, small dependency set, and README provide basic consumer context. The repository is not archived, but its lone-maintainer profile limits confidence in future fixes.
38%
Total Score
25
60
50
Health Score Breakdown
The package has only two releases, with the latest published in March 2021 and none in the last 12 months, indicating prolonged inactivity.
The repository recorded no commits and no active maintainers in the last three months, reinforcing that maintenance has effectively stopped.
Only one registry account has publish access. The repository is user-owned rather than organization-backed, so there is little visible publishing redundancy if that maintainer becomes unavailable.
The linked repository name does not match the package name and its README does not mention the package, creating uncertainty that it is the intended source repository.
Composer is used for builds, but no security scanning tooling is present, reducing automated visibility into dependency or source risks.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 iSakura |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 stephenhill/base58 Version >=1.1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.