The project has useful structure, tests, release tracking, and clear licensing. Its large dependency surface, install-time scripts, missing security policy, and package/repository naming mismatch add maintenance and ownership concerns.
35%
Total Score
50
50
67
50
The latest release was published in November 2017, with no releases in the last 12 months and only eight releases overall. This long release gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push being over eight years ago. There is no observed recent maintenance to offset the age of the release.
The package declares 53 runtime dependencies for an ERP application, creating a substantial compatibility and maintenance burden. Its application-sized scope partly explains the count but does not remove the long-term risk.
The package runs post-install and post-update Composer scripts, so installation and upgrades execute package-controlled behavior. No provided signal shows that these hooks are unnecessary or narrowly scoped.
The linked repository name does not match the package name and its README does not mention the package. This makes package ownership less transparent, even though the shared organization provides some context.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.5 | — | — |
doctrine/dbal Version ^2.5 | — | — |
sylius/sylius Version ^1.0 | — | — |
symfony/symfony Version ^3.3 | — | — |
jms/serializer-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.