A substantial README, repository tests, and a changelog improve transparency. The workflow has three unpinned actions, while the repository has no security policy or scanning tools.
42%
Total Score
0
60
50
The latest release was published about five years ago, and there were no releases in the last 12 months. This indicates substantial abandonment risk despite 30 total releases.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and limited evidence of ongoing maintenance.
The manifest declares MIT, but the artifact license file is detected as GPL-3.0. This unresolved mismatch creates a material adoption and compliance concern, although a license file is present.
Composer build tooling is present, but no security scanning tools were detected. This modestly limits evidence of automated security hygiene.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it is less significant than the maintenance and licensing concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
google/apiclient Version ^2.1 | — | — |
illuminate/console Version ~5.8.0|^6.0|^7.0|^8.0 | — | — |
illuminate/support Version ~5.8.0|^6.0|^7.0|^8.0 | — | — |
illuminate/filesystem Version ~5.8.0|^6.0|^7.0|^8.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.