The project has a clear README and a matching source repository. It lacks tests and security scanning, and its workflow uses two unpinned actions.
45%
Total Score
25
100
69
75
The package has only two releases, both made about 370 days ago, with no releases in the last 12 months. This is strong evidence of a stagnant release process for a young package.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with no releases in the last year, this materially raises abandonment risk.
The package and repository are owned by an individual rather than an organization. That is not inherently unhealthy, but it provides no broader backing to compensate for the thin maintenance activity.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers confidence in external adoption but is not decisive for a small package.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest repository hygiene gap rather than evidence that the package is unsafe.
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.