Tests, a README, and a declared license provide useful basic coverage. However, the lack of a security policy and scanning leaves maintenance risk less visible, alongside the long inactivity.
38%
Total Score
25
72
75
There has been only one release, published about 10 years ago, with no releases in the last 12 months. This strongly suggests the package is not actively maintained.
There were zero commits and zero active maintainers in the last three months. Combined with the last push being about 10 years ago, this is strong evidence of abandonment risk.
The repository is owned by an individual rather than an organization, so there is no visible organizational backing to compensate for the thin maintenance history.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of an active user community.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces supply-chain hygiene, though it is secondary to the much older inactivity signal.
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.