The package has been unchanged since its first release 425 days ago, and every GitHub Action reference is unpinned. Organization backing, tests, a changelog, and a security policy provide useful maintenance structure, but do not offset the inactive release history.
58%
Total Score
75
86
75
A post-autoload-dump lifecycle script runs during installation. This adds execution surface to dependency installation, but the signal does not show that the script is harmful or unusually broad.
This is the sole release, published 425 days ago, with no releases in the last 12 months. That leaves maintenance and compatibility uncertain for a package developers may need to keep current.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the single-release history and indicating a real abandonment risk.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
All three workflows were analyzed with no reported audit findings or untrusted checkouts, but all 8 action references are unpinned and two workflows grant top-level write permissions. The unpinned actions reduce build reproducibility, while the write permissions are a moderate hygiene concern without an identified untrusted trigger.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.