Its broad dependency set and install-time scripts add upgrade and maintenance friction. The stable version and unarchived repository help, but the project shows no activity since June 2017 and has almost no supporting project material.
30%
Total Score
0
50
75
50
The package has only two releases, with the latest published in June 2017 and none in the last 12 months. That is strong evidence of abandonment for a dependency expected to remain compatible with its ecosystem.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last release being over nine years ago. No provided activity signal compensates for this absence.
The package declares 16 runtime dependencies, including framework, ORM, security, and API components. That broad surface increases compatibility and maintenance exposure when the package has not been updated for over nine years.
post-install-cmd and post-update-cmd scripts run during dependency installation and updates, adding execution and reproducibility risk. Their presence is not severe by itself, but it increases the cost of adopting an otherwise inactive package.
Both the published artifact and linked repository contain only composer.json, leaving little visible source or project context for a package with 16 runtime dependencies. This materially limits transparency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.4.5 | — | — |
symfony/flex Version ^1.0 | — | — |
symfony/yaml Version ^3.3 | — | — |
symfony/asset Version ^3.0 | — | — |
symfony/console Version ^3.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.