The package has repository tests, a changelog, and a clear MIT license. Its four workflow actions are unpinned, and no repository security policy or security scanning is present.
57%
Total Score
75
100
88
67
This package has made only one release, with no further release in about 14 months. That limits evidence of ongoing maintenance and makes adoption more dependent on the initial implementation.
The repository had zero commits and zero active maintainers in the last three months. Combined with the single-release history, this is meaningful evidence that maintenance has slowed or stopped.
The repository uses Composer build tooling, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe dependency risk.
No security policy is published, leaving no documented process for reporting or handling vulnerabilities. This lowers transparency for a package that makes network API requests.
The only workflow was fully analyzed with no dangerous triggers or audit findings, but all four action references are unpinned. That leaves avoidable build-integrity exposure, while the absence of a top-level permissions block is not a concern on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
peso/core Version ^1.1 | — | — |
psr/http-client Version ^1 | — | — |
psr/http-factory Version ^1 | — | — |
psr/simple-cache Version ^1 || ^2 || ^3 | — | — |
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.