The MIT license, matching repository, and organization backing improve transparency. Recent activity is minimal and concentrated in one contributor, so maintenance capacity remains a concern.
56%
Total Score
67
100
71
75
The latest registry release was about 7 years ago, with no releases in the last 12 months. This is a substantial maintenance concern despite 22 historical releases and a previously regular cadence.
All recent commit activity came from one contributor. Organization ownership provides some handoff capacity, but the observed recent maintenance remains concentrated.
Only one commit was recorded in the last 3 months, showing very limited current development activity. This partly offsets the old release history but does not demonstrate an active release process.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene limitation rather than evidence of abandonment.
The repository has no security policy. That reduces transparency for vulnerability reporting and response, although it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1 | — | — |
ramsey/uuid Version ^3 | — | — |
formapro/values Version ^0.5 | — | — |
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.