The package is clearly documented, tested in its repository, and backed by an unarchived organization-owned project. Its registry release history has gone quiet and recent repository activity is absent, so maintenance may be slowing; workflow references also lack pinning.
62%
Total Score
75
100
88
67
The latest registry release was about 17 months ago, with no releases in the last 12 months. That is a meaningful maintenance concern, although the package has 14 releases and is not deprecated.
There were no commits and no active maintainers in the last 3 months. Combined with no registry releases in the last year, this raises the risk of slowing maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence of an unsafe release by itself.
The repository has no security policy. That weakens the project's documented vulnerability-reporting process, though it does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 5 action references are unpinned. Unpinned actions leave the build exposed to upstream reference changes and are a hygiene concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/cache Version ^1.0 || ^2.0 || ^3.0 | — | — |
middlewares/utils Version ^4 | — | — |
mikespub/micheh-psr7-cache Version ^2.0 | — | — |
psr/http-server-middleware Version ^1 | — | — |
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.