The small project has had no commits in the last three months and no release in the last year, which limits confidence in ongoing maintenance. Its tests, README, release notes, license, and direct repository match provide useful transparency, while the workflow uses five unpinned actions.
68%
Total Score
67
100
88
83
The repository is owned by an individual rather than an organization, so the single registry maintainer is consistent with the project’s backing but leaves limited visible redundancy.
The package has existed since 2017 with 10 releases, but it has had no release in the last year; this is a maintenance concern for a dependency.
There were no commits and no active maintainers in the last three months, indicating currently quiet maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-factory Version ^1.0 | — | — |
psr/http-message 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.