The MIT declaration, README, and focused source tree make the package easy to inspect. Its single-user ownership and lack of security tooling reduce confidence in ongoing care; pin this version only if its narrow interfaces remain sufficient.
42%
Total Score
25
79
50
Only two releases exist, with the latest published more than five years ago and no releases in the last 12 months. This is strong evidence of a dormant project, with no newer release activity to offset it.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but that does not compensate for the absence of observed maintenance.
One registry maintainer provides a thin ownership base for a package that has shown no recent release or commit activity. The matching repository owner gives some continuity but does not demonstrate ongoing capacity.
Composer build tooling is present, which fits the package ecosystem, but no security scanning tools were observed. This is a transparency and maintenance-hygiene gap rather than a severe risk on its own.
The linked repository has no security policy. For a small focused package this is a modest disclosure gap, but it provides no documented channel or process for handling vulnerabilities.
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.