The workflow is fully audited, uses read-only job permissions, and the release includes tests and detailed release notes. No repository security policy or automated security scanning is present, leaving transparency and defensive maintenance weaker than the rest of the project.
78%
Total Score
83
100
93
75
One contributor made all seven commits in the last three months, creating a narrow recent maintenance base. Organization backing provides some handoff capacity, but the observed activity is still concentrated.
Composer build tooling is present, but no security scanning tools were detected. For a maintained library this is a modest defensive-maintenance gap rather than evidence of abandonment.
The repository has no security policy. That weakens vulnerability-reporting transparency, though the active repository, tests, and release process provide compensating project evidence.
The single workflow was fully analyzed with no failed files, no untrusted checkouts, no script injection, and read-only permissions. However, all three action references are unpinned, which leaves avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.1 || ^2.0 || ^3.0 | — | — |
guzzlehttp/guzzle Version ~7.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.