The project has clear ownership, a matching repository, and a documented release, while its MIT licensing and dependency structure are straightforward. The repository has no security policy, and its only workflow uses a broad write token with an unpinned action.
61%
Total Score
67
100
94
75
Only three releases exist, with no release in the last 12 months; the latest release was published about 21 months ago. This is meaningful maintenance risk, although the package may be intentionally stable.
There were no commits and no active maintainers in the last three months, reinforcing the concern raised by the lack of recent releases.
There were no new issues or pull requests in the last month and no merged pull requests, indicating little recent project activity, though the issue count itself is unknown.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear.
The single workflow uses a pull_request_target trigger without an untrusted checkout or script injection, but grants top-level write permissions and uses its only action unpinned. These are moderate workflow hygiene weaknesses, not severe evidence on their own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr-discovery/log-implementations Version ^1 | — | — |
psr-discovery/cache-implementations Version ^1 | — | — |
psr-discovery/container-implementations Version ^1 | — | — |
psr-discovery/http-client-implementations Version ^1 | — | — |
psr-discovery/http-factory-implementations 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.