The package is well documented and tested, with a long release history and organizational ownership. Maintenance is currently concentrated in one contributor, while workflow permissions, unpinned actions, and an untrusted checkout add avoidable supply-chain exposure.
68%
Total Score
75
100
94
83
All 9 analyzed action references are unpinned, and one workflow combines pull_request_target with an untrusted checkout; the two workflows with top-level write permissions further widen credential scope. The audit completed cleanly with no reported high-confidence findings, but these workflow choices remain meaningful supply-chain hygiene risks.
All recent commits came from one contributor, creating a concentrated bus factor. Organizational ownership partly mitigates handoff risk but does not remove the current dependence on one active contributor.
Only 2 commits were made in the last 3 months by one active maintainer. This shows some recent work but a thin current maintenance base.
Composer build tooling is present, but no security scanning tools were detected, leaving a maintenance and security-hygiene gap.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
google/cloud-tasks Version ^2.0 | — | — |
thecodingmachine/safe Version ^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.