Clear usage documentation, tests, and a recent security-fix release support adoption. The workflow's six unpinned actions and absent security policy leave meaningful maintenance and build-integrity gaps.
72%
Total Score
50
100
86
75
Only one registry account can publish the package. The matching user-owned repository and small project scope make this understandable, but it still creates a limited publishing and maintenance base.
The package has only three releases since June 2023, with a median interval of about 590 days and one release in the last 12 months. The current release shows activity, but the historically sparse cadence limits maintenance confidence.
The repository recorded zero commits and zero active maintainers in the last three months. Although the release is current, the lack of recent commit activity weakens evidence of ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That leaves a modest gap in automated security hygiene.
The repository has no security policy. For a middleware that renders data into JavaScript, the absence of a documented vulnerability-reporting process is a meaningful transparency gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-server-middleware Version ^1.0 || ^2.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.