The package has tests, useful documentation, a matching MIT license, and no install-time scripts. Its lone maintainer and more than three years without a release or commit activity raise maintenance risk, while the workflow uses three unpinned actions and lacks security scanning.
56%
Total Score
50
100
88
67
Only one account has registry publish access. That is a thin publishing base and increases continuity risk when combined with the inactive repository.
The package has 11 releases over a long history, but it has had no release in more than three years, which weakens confidence in ongoing maintenance.
There were no commits and no active maintainers in the last three months; alongside the old last push, this is strong evidence of inactive maintenance.
Composer build tooling is present, but no security scanning tools are configured, leaving a transparency and maintenance-hygiene gap.
The repository has no security policy, making vulnerability reporting and maintainer response expectations less clear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-message 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.