The project has tests, release notes, and organizational ownership. Recent activity is absent, security documentation is missing, and most workflow actions are unpinned.
60%
Total Score
83
100
88
67
The package is about 2 years and 9 months old but has only four releases, with one release in the last 12 months. That indicates a sparse release cadence, although the latest release is recent enough to avoid an abandonment verdict by itself.
The repository recorded zero commits and zero active maintainers in the last three months. This is concrete evidence of currently quiet development and raises maintenance risk.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest transparency and maintenance gap.
The repository has no security policy. That weakens the project's documented process for receiving and handling security reports.
All five workflows were analyzed successfully with no reported audit findings or dangerous trigger sinks, and none use top-level write permissions. However, 7 of 12 action references are unpinned, leaving avoidable build-integrity exposure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3 | — | — |
horde/util Version ^3 || dev-FRAMEWORK_6_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.