The package is minimal, stable, and easy to inspect, with one runtime dependency and a matching source repository. Its only release was over three years ago and the repository shows no recent commits, so future fixes are uncertain.
58%
Total Score
50
100
88
83
Only one registry maintainer is listed, and the project is user-owned rather than organization-backed. That indicates a thin publishing base, though it is not by itself evidence of abandonment.
There has been only one release, published over three years ago, with no releases in the last 12 months. This is meaningful evidence of limited maintenance and raises uncertainty about future fixes.
The repository had zero commits and zero active maintainers in the last three months. Combined with the single-release history, this points to a real maintenance and abandonment concern.
Composer build tooling is present, but no security-scanning tools were detected. For this small package that is a minor transparency gap, not a severe supply-chain concern.
The repository has no published security policy. This modestly limits vulnerability-reporting transparency, although the package's small scope reduces the practical impact.
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.