The organization-backed repository matches the package and documents it in its README. Composer packaging is present and there are no install scripts, but maintenance appears dormant and the project has no security policy or automated tests.
55%
Total Score
50
78
83
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push being over three years ago. This materially raises abandonment risk.
The package artifact lacks a README, tests, and changelog, while the repository also reports no tests or changelog. The repository file tree does contain a README, so the missing artifact README is a minor consumer-documentation gap rather than evidence of abandonment.
There has been only one release, 1.0.0, published about 4 years and 5 months ago, with no releases in the last 12 months. This is strong evidence of a small or dormant project and limits confidence in ongoing maintenance.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of a broad support community.
The repository uses Composer, showing basic build tooling, but it has no security-scanning tools. The missing scanning is a hygiene gap, not a standalone reason to reject the release.
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.