The package has a clear license, README, and release notes, and its repository remains available under an organization. It has no security policy or security scanning, so pinning this older release deserves extra care.
52%
Total Score
50
100
75
75
The package has had no registry release in nearly six years, with no releases in the last 12 months. This is substantial evidence of abandonment risk despite the repository receiving a later push.
There were no commits and no active maintainers in the last three months. Combined with the stale registry release history, this materially raises maintenance risk.
The repository uses Composer build tooling, but no security scanning tools are reported. The missing scanning is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The linked repository is not archived and was pushed in 2023, providing evidence that the project was not formally abandoned. However, that activity is still over three years old relative to this assessment.
The repository has no security policy. Consumers have no documented security-reporting process, which weakens project transparency for a package handling application infrastructure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pimcore/pimcore Version >=6.0 <7.0 | — | — |
symfony/messenger Version ^4.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.