Clear documentation, tests, licensing, and a stable release line reduce adoption friction. The small public footprint and limited security process warrant ownership-aware maintenance planning.
68%
Total Score
67
100
94
67
One contributor made all recent commits, creating a concentrated maintenance dependency; organization ownership provides some handoff capacity but does not remove the concentration concern.
Only two commits were recorded in the last 3 months, which is limited activity for a package releasing frequently and leaves less evidence of sustained development.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy, so users have no documented security-reporting or response process.
The workflow audit completed cleanly with no dangerous triggers or audit findings, but all three action references are unpinned, which weakens build reproducibility and update control.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
psr/simple-cache Version ^3.0 | — | — |
monkeyscloud/monkeyslegion-entity Version ^2.0 | — | — |
monkeyscloud/monkeyslegion-database Version ^2.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.