The package includes a README, tests, and an MIT declaration, which help consumers understand and use it. Its single maintainer, absent security policy and scanning, and very small user base leave limited evidence of ongoing support.
43%
Total Score
25
81
50
This is the package's only release, published about five years ago, with no releases in the last 12 months. That provides strong evidence of abandonment risk, despite the stable 1.0.0 version.
The repository recorded no commits and no active maintainers in the last three months, consistent with the roughly five-year gap since the last release. This materially weakens confidence in ongoing maintenance.
One registry maintainer creates a thin publishing base and increases continuity risk if that person stops maintaining the package. The linked repository is user-owned, so there is no organizational backing shown to offset this.
Composer build tooling is present, but no security scanning tools were detected. That is a modest repository hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is less significant than the clear maintenance slowdown.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.0 | — | — |
symfony/config Version ~4|~5 | — | — |
symfony/console Version ~4|~5 | — | — |
symfony/http-kernel Version ^4.0 || ^5.0 | — | — |
symfony/dependency-injection Version ^4.0 || ^5.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.