The repository includes tests and a matching README, and the package has no install-time scripts. Its very small footprint limits exposure, but the long release gaps, no recent commits, and unpinned workflow actions make maintenance and build reproducibility less reassuring.
62%
Total Score
50
100
81
75
The repository is owned by an individual account rather than an organization, so there is no provided evidence of organizational continuity to offset the limited recent commit activity.
The package has existed for over 6 years but only 4 releases, with a median interval of about 2 years 7 months; 2 releases in the last 12 months show recent publishing activity, but the overall cadence is sparse.
The repository recorded zero commits and zero active maintainers in the last 3 months. This is concerning for ongoing maintenance, although the recent January release provides some counterevidence of activity.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest security-process gap for a small package.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
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.