Security scanning is absent, and the repository has no tests; the README and MIT licensing make the small package straightforward to inspect. Its dependency footprint is minimal, but that does not offset the maintenance concern.
38%
Total Score
0
100
71
75
The latest of only 3 releases was published more than 5 years ago, with 0 releases in the last 12 months. This is strong evidence of abandonment for a package intended as an application dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and leaving current compatibility issues unlikely to be addressed.
The repository has 0 stars and 0 forks, with 1 watcher. Popularity is only supporting evidence, but these very limited adoption signals provide little evidence of an active community or review base.
Composer build tooling is present, but no security-scanning tools are configured. The small package remains inspectable, yet automated detection of dependency or code issues is limited.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported. This is a meaningful hygiene gap, though it is less serious than the inactive maintenance record.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.