The README, release notes, and matching repository make this small package straightforward to identify and consume. Maintenance is currently quiet, with one publisher and no commits in the last three months; the absent security policy adds a smaller transparency concern.
64%
Total Score
50
86
83
One registry publisher is consistent with a small user-owned project, but it also indicates limited publishing capacity when combined with the lack of recent commits.
The repository recorded zero commits and zero active maintainers in the last three months. That quiet period lowers confidence that defects or compatibility changes will receive prompt attention.
Composer build tooling is present, but no security-scanning tools were detected. For this small package the missing scanner is a hygiene gap, not evidence of unsafe code.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency weakness, but it does not by itself make the release unfit to use.
v0.5.2 is not a prerelease, but the package remains below version 1.0, so its public API may still change. This is a moderate maturity consideration rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.