The project has a long release interval and no commits in the last three months. Repository tests, licensing, and static analysis provide useful supporting evidence.
64%
Total Score
50
86
75
The package has 7 releases over about 6 years, with a median interval of about 12 months and 1 release in the last 12 months. The recent 1.1.0 release shows the project is not abandoned, but maintenance is infrequent.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The recent release partly offsets this, but the current activity does not demonstrate an actively maintained project.
The repository name does not exactly match the package name, and no README package mention was collected. Organization backing and the matching repository URL reduce concern, but package ownership is less transparent than ideal.
The single workflow was fully analyzed, but all 4 action references are unpinned and a high-confidence finding reports a container using the floating `latest` tag. This weakens build reproducibility, though no untrusted checkout, script injection, or broad write permission was found.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.1 || ^2.0 | — | — |
psr/http-factory Version ^1.0 | — | — |
psr/http-message Version ^1.0 || ^2.0 | — | — |
fig/http-message-util Version ^1.1 | — | — |
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.