Licensed artifacts, tests, release notes, and a stable major version provide useful maintenance context. The single registry maintainer is backed by an organization-owned repository, but pin this version because the project has no recent activity.
42%
Total Score
50
75
50
The package has had no releases in the last 12 months, and its latest release was over seven years ago. This is strong evidence of abandonment risk despite 21 historical releases.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. No provided activity signal compensates for this inactivity.
The repository name does not match the package name and its README does not mention the package, so the source-to-artifact relationship is unclear. This creates a meaningful transparency concern even though the repository owner is an organization.
The project uses Composer, but no security-scanning tooling was detected. That is a modest hygiene gap and adds concern alongside the absence of recent maintenance.
The linked repository has no security policy. For a dependency-injection library, this weakens the project's published process for handling security reports, though it does not by itself show unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jms/metadata Version ^2.0 | — | — |
jms/aop-bundle Version ~1.3 | — | — |
symfony/finder Version ~3.0|~4.0 | — | — |
symfony/process Version ~3.0|~4.0 | — | — |
symfony/routing 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.