The package has a small, tested codebase and clear ownership, but its maintenance signals are weak. Its early-version status, very limited adoption, and missing security policy add uncertainty for a new dependency.
42%
Total Score
67
64
83
The latest release was in June 2020, with no releases in the last 12 months and only four releases overall. This long release gap is strong evidence of abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the release history and indicating a serious lack of current maintenance.
Four stars and one fork indicate a very small user and contributor base. Popularity is only supporting evidence, but this offers little external maintenance capacity to offset inactivity.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a standalone severe risk.
The repository has no security policy, reducing guidance for reporting and handling vulnerabilities. This matters more alongside the absence of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ~2.5 | — | — |
doctrine/data-fixtures Version 1.3.* | — | — |
container-interop/container-interop 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.