The repository still documents the project and includes tests, but recent development activity is absent and the CI workflow uses a floating container image. The missing security policy adds a smaller transparency concern.
58%
Total Score
50
100
88
83
The package and repository share the designcise owner, but the repository is user-owned rather than organization-backed; this provides direct ownership alignment without strong evidence of a broad maintainer base.
The package has 22 releases since 2018, but its latest registry release was over three years ago and there were no releases in the last 12 months, which raises maintenance risk.
There were no commits and no active maintainers in the last three months, which weakens evidence of ongoing maintenance even though the repository was pushed recently.
Composer build tooling is present, but no security-scanning tool was detected; this is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a framework package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^2.0 | — | — |
psr/http-factory Version ^1.0 | — | — |
psr/http-message Version ^2.0 | — | — |
psr/http-server-middleware Version ^1.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.