The source repository includes tests, a clear license, and a focused dependency set. Its only release was 105 days ago and no commits were recorded in the last three months; all workflow actions are unpinned and no security policy is present.
58%
Total Score
50
100
86
50
This is a young package with one release, published 105 days ago, so there is too little release history to demonstrate sustained maintenance. Its recent origin partly explains the limited history but does not remove the uncertainty.
The repository recorded zero commits and zero active maintainers in the last three months. For a package only 105 days old, that is a meaningful sign that maintenance may already have stalled.
Composer build tooling is present, but no security scanning tools were detected. The missing scanner is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled. This is a maintenance and response gap, not a verdict about maliciousness.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all three action references are unpinned. Unpinned actions weaken build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^7.9 | — | — |
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.