Clear documentation, tests, release notes, and licensing make integration easier. The dependency footprint and lack of security tooling add upkeep concerns for a small project with limited recent activity.
56%
Total Score
50
50
88
50
Seven runtime dependencies, including Symfony, Doctrine, JMS Serializer, LiipImagine, and VichUploader integrations, create meaningful compatibility and maintenance surface for consumers.
The package has 17 releases since 2016, but none in the last 12 months and its latest release was about four years ago. This is a meaningful maintenance concern, though the release history shows prior maturity.
There were zero commits and zero active maintainers in the last three months, consistent with the latest release being about four years ago. This materially increases the risk that issues and compatibility changes will go unaddressed.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This is a documentation gap that matters for a maintained integration library.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.5 | — | — |
symfony/yaml Version ^4.0|^5.0 | — | — |
liip/imagine-bundle Version ^1.8|^2.3 | — | — |
vich/uploader-bundle Version ^1.5 | — | — |
jms/serializer-bundle Version ^3.0|^4.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.