The repository includes tests, a README, and release notes, while organization backing and a matching package repository reduce uncertainty. Missing licensing and security documentation still matter for adoption.
43%
Total Score
75
100
81
83
No license is declared, and neither the package nor repository contains a license file. This creates a real adoption and redistribution risk.
The package has made no release in more than 6 years, despite eight releases overall, which is a substantial maintenance concern for a dependency.
There were zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and indicating that abandonment risk is substantial.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence of unsafe behavior.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
level-2/dice Version ^4.0 | — | — |
level-2/maphper Version ^0.9 | — | — |
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.