The MIT license, tests, and organization backing provide useful baseline transparency. Its repository has no security policy, and the linked project does not identify this package in its README, adding adoption uncertainty.
30%
Total Score
0
60
50
The last release was over ten years ago, despite 118 historical releases; there have been no releases in the past 12 months. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers over the past three months, consistent with the release gap and indicating no current maintenance capacity.
The linked repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less clear than expected. Organization backing and the package README provide some context but do not remove that uncertainty.
The repository is not archived, which is a modest compensating signal, but its last push was over ten years ago and does not offset the lack of current activity.
No repository security policy was found. This is a transparency and maintenance gap, though it is secondary to the much longer-standing inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.5 | — | — |
symfony/config Version ^2.7|^3.0 | — | — |
doctrine/common Version ^2.5 | — | — |
elcodi/newsletter Version ^2.0 | — | — |
elcodi/core-bundle Version ^2.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.