Clear licensing, documentation, tests, and release notes support adoption. Workflow references are unpinned and the repository has no security policy, so maintenance safeguards are thinner than ideal.
72%
Total Score
75
88
67
The project is mature, with 70 releases over roughly 11 years, but only one release in the last 12 months and a median interval of about 7 days indicate a recently slower cadence.
The repository recorded zero commits and zero active maintainers in the last three months. This is a meaningful maintenance concern, although the recent release and long project history partly offset it.
Composer build tooling is present, but no security scanning tool was detected. For a maintained API client, the missing automated security scanning is a modest safeguard gap.
The repository has no security policy. This weakens transparency about vulnerability reporting and handling, though it does not by itself indicate abandonment.
Both workflows were analyzed successfully and had no detected dangerous sinks or audit findings. However, all three action references are unpinned, leaving them exposed to upstream action changes.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
brick/math Version ^0.14.1 | — | — |
ramsey/uuid Version ^4.7 | — | — |
symfony/config Version ^6.4|^7.4 | — | — |
beberlei/assert Version ^3.3 | — | — |
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.