Documentation, tests, licensing, and release notes are all present. The repository lacks security scanning, and its three workflow actions are unpinned.
72%
Total Score
75
94
50
There were zero commits and zero active maintainers in the last three months. Although a release occurred during that period, the lack of observed development activity raises maintenance and abandonment concerns.
The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. This makes vulnerability reporting and response expectations less transparent, though the project remains maintained and has clear licensing and documentation.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all three action references are unpinned, which leaves the workflow exposed to upstream reference changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
gettext/gettext Version ^4.8.4 | — | — |
gettext/languages Version <=2.6.0 | — | — |
guzzlehttp/guzzle Version >=6.3 | — | — |
illuminate/config Version >=5.5 | — | — |
illuminate/console Version >=5.5 | — | — |
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.