Commit activity has stopped after the initial release burst, and the repository has little adoption or security tooling. A substantial README, repository tests, matching source, and clear MIT licensing provide useful transparency.
64%
Total Score
50
75
50
The package is about five months old with five releases, all within roughly one week and a median interval of about eight hours. This shows an active launch period but not yet a sustained maintenance record.
The repository recorded no commits and no active maintainers in the last three months, despite being a young project. The recent push associated with the latest release provides only limited evidence of ongoing maintenance.
The repository has three stars, no forks, and no watchers. Popularity is only supporting evidence, but these counts provide little external validation for a new dependency.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance gap for a package intended to handle HTTP application runtime behavior.
The repository has no security policy. This makes vulnerability-reporting expectations less clear, although the absence does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
nih/router Version ^0.2.0 | — | — |
nih/container Version ^0.1.3 | — | — |
psr/http-factory Version ^1.1 | — | — |
psr/http-message Version ^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.