Usable with caveats: it is actively released, well-documented, tested, and not deprecated or archived. The project is only 173 days old and all recent commits come from one contributor, so long-term continuity remains uncertain.
72%
Total Score
75
100
88
90
The registry namespace and repository owner match, but the owner is an individual account rather than an organization, so there is no organizational handoff capacity to offset the single-contributor risk.
All six recent commits came from one contributor, leaving maintenance highly dependent on a single person with no demonstrated backup contributor.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a transparency gap, though it is not by itself evidence of unsafe code.
The repository has no security policy, so the process for reporting and handling vulnerabilities is unclear.
Version 0.6.0 is not a stable major release, so the API may still change, although it is not marked as a prerelease and recent releases have been consistent.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tuupola/base62 Version ^2.1 | — | — |
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.