The stable 1.0.1 release includes tests, release notes, and an MIT license, while its two runtime dependencies keep the package straightforward. Organization backing and a matching repository help, but security tooling is absent.
54%
Total Score
50
100
81
83
The package has only two releases, both around 10 years ago, with none in the past 12 months. This is strong evidence of stagnation, although the stable version may be intentionally complete.
There were no commits or active maintainers in the past three months, and the repository was last pushed about five years ago. This materially raises abandonment risk.
Composer is used for the build, but no security-scanning tool is configured. That is a transparency and maintenance-hygiene gap, not evidence that the package is unsafe.
The repository has no security policy. For a small library this is a modest disclosure-process gap, but it reduces transparency if vulnerabilities are found.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/collections Version ~1.0 | — | — |
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.