The small dependency set, MIT licensing, tests, and clear package contents reduce adoption friction. Maintenance evidence is thin: only two releases landed on the same day, with no commits in the last three months, while workflow references are unpinned and no security policy is present.
65%
Total Score
75
100
89
83
One registry maintainer is consistent with the repository being owned by an individual; the small maintainer base still leaves limited visible redundancy.
There are only two releases, both published on the same day, so the package has limited demonstrated release history and no established cadence.
The repository recorded zero commits and zero active maintainers in the last three months, which is a meaningful maintenance and abandonment concern for a package released only recently.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.
No repository security policy was found, reducing transparency about how users should report vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.0 || ^2.0 || ^3.0 | — | — |
psr/clock Version ^1.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.