Clear documentation, release notes, repository tests, and a modest dependency set support adoption. The long pause in development and unpinned workflow actions leave meaningful maintenance and build-integrity concerns.
56%
Total Score
50
100
75
75
Only three releases were published, with none in the last 12 months; the latest release was over three years ago. This is meaningful evidence of stalled maintenance.
The repository had no commits and no active maintainers in the last three months, consistent with a project that has been inactive for over three years.
The repository is owned by an individual rather than an organization, so the single registry maintainer represents a genuinely thin ownership base alongside the long inactivity period.
Composer is used for builds, but no security scanning tool was detected. That is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/ca-bundle Version ^1.3 | — | — |
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.