Clear documentation, tests, and a clean workflow audit support predictable use. The project lacks a security policy, and all recent commits come from one maintainer.
78%
Total Score
67
94
83
The repository is owned by an individual user rather than an organization, so the single-maintainer concentration is not offset by visible organizational backing.
All 29 recent commits came from one maintainer, so maintenance continuity depends heavily on a single person and is a genuine resilience concern.
Composer build tooling is present, but no security-scanning tools were detected; this is a modest transparency gap rather than evidence of unsafe behavior.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The only workflow uses read-only permissions and has no flagged audit findings, but its sole action reference is unpinned, weakening reproducibility and update integrity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.0 || ^2.0 | — | — |
psr/http-message Version ^1.1 || ^2.0 | — | — |
middlewares/utils Version ^4.0.2 | — | — |
ctw/ctw-middleware Version ^5.0 | — | — |
psr/http-server-handler 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.