Its MIT licensing and matching repository make provenance clear, while Composer is the only build tooling and no security scanning is present. The small project has no tests and only six runtime platform requirements, limiting evidence for long-term maintenance.
55%
Total Score
0
72
75
The package has had only two releases, both in November 2022, with no release in roughly three years and eleven months. This is strong evidence of abandonment risk, although the stable 2.0.0 version reduces upgrade uncertainty.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no development since November 2022. The repository is not archived, but current maintenance capacity is not demonstrated.
The artifact includes a README, but neither the published package nor repository reports tests or a changelog. The README helps consumers, while the lack of tests limits confidence in future fixes and compatibility.
The repository has 2 stars, 0 forks, and 1 watcher, providing little community evidence or backup if maintenance is needed. Low popularity alone is not disqualifying for a small utility, so this is a modest concern.
Composer is used for the build, which is appropriate for a Packagist package, but no security scanning tools are configured. The missing scanning reduces maintenance hygiene without indicating an immediate dependency risk.
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.