The package is small, clearly identified, licensed, and documented for consumers. Its sole release is over a year old, with no recent commits, tests, security scanning, or security policy, so future maintenance is uncertain.
58%
Total Score
50
88
75
One registry maintainer is consistent with a small, user-owned project, but it leaves the package dependent on a single publisher without demonstrated recent activity.
There has been only one release, published about 17 months ago, with no releases in the last 12 months. This is meaningful abandonment risk for a dependency, despite the stable v1.0.0 version.
The repository recorded zero commits and zero active maintainers during the last three months. Its small scope may reduce the need for frequent changes, but there is no observed evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance gap, though the package is small and no active supply-chain workflow was observed.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This is a modest transparency concern rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version ^2.15 | — | — |
symfony/config Version ^6.4 | — | — |
symfony/http-kernel Version ^6.4 | — | — |
doctrine/annotations Version ^2.0 | — | — |
symfony/http-foundation Version ^6.4 | — | — |
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.