The package is clearly licensed and its repository matches the package, which improves transparency. Its small README and absent security policy leave limited guidance for adoption.
38%
Total Score
50
80
50
The artifact includes a README, but it is only 28 characters long and provides little integration guidance. The absence of tests and a changelog in the published package is normal packaging practice and is not a gap by itself.
The package has only one release, published about 10 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last 3 months, and its last push was about 6 years ago. The lack of recent work materially lowers confidence in maintenance.
The linked repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it is not severe on its own.
The single analyzed workflow is complete and has no reported audit findings or untrusted execution paths, but its only action use is unpinned. That creates a modest reproducibility and supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pimple/pimple Version ~3.0 | — | — |
doctrine/cache Version ~1.4 | — | — |
monolog/monolog Version ^1.17 | — | — |
guzzlehttp/guzzle Version ~6.0 | — | — |
symfony/http-foundation Version ~2.6|~2.7|~2.8|~3.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.