Documentation, tests, licensing, and a security policy make the project transparent to integrate. Pin v0.1.0 and expect the maintenance model to remain small until more releases and contributors appear.
68%
Total Score
75
100
79
100
The package is only 50 days old and has one release, so there is not yet enough history to demonstrate sustained maintenance. Its recent initial release is consistent with a genuinely new project rather than abandonment.
All three commits in the last three months came from one contributor, so maintenance is concentrated. Organization backing provides some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tool was detected. For a new dependency this is a modest process gap, not evidence of abandonment by itself.
v0.1.0 is not a stable major release, which indicates an API may still change. The presence of a GitHub release and release notes provides some transparency but does not offset the early maturity stage.
All four workflows were analyzed with no audit findings, untrusted checkouts, or script injections. However, three workflows grant top-level write permissions and all seven action references are unpinned, creating moderate workflow hygiene and reproducibility concerns without an untrusted trigger sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^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.