The package is small, clearly licensed, documented, and has no install-time scripts. Its single-maintainer project has had no release for over four years or commits in the last three months, while no security policy is published, making future fixes uncertain.
58%
Total Score
50
100
88
75
One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing capacity if that maintainer becomes unavailable.
The latest release was over four years ago, and there have been no releases in the last 12 months. Its nine releases show an established package, but the long pause raises maintenance concerns.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long release gap, this points to a genuinely inactive project rather than merely infrequent releases.
Composer build tooling is present, but no security-scanning tooling was detected. For a small package this is a modest transparency and maintenance gap, not a standalone adoption blocker.
The repository has no security policy. This weakens the documented process for reporting and handling vulnerabilities, although the package's small scope limits the significance of the gap.
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.