Tests, release notes, and an MIT declaration provide useful baseline transparency. The single maintainer and unpinned workflow references leave limited operational margin.
62%
Total Score
50
79
75
Only one registry account has publish access, which creates a thin publishing base; the linked repository is user-owned rather than organization-backed.
The repository recorded zero commits and zero active maintainers in the last three months, a maintenance concern; the recent push and release provide only limited compensation.
The repository name does not match the package name and its README does not mention the package, so ownership of the published package is less transparent than expected.
The repository uses Composer for builds, but no security scanning tools were detected, leaving a modest assurance gap.
No security policy was found in the repository, reducing transparency for reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
statamic/cms Version ^6.0 | — | — |
laravel/framework Version ^12.0 || ^13.0 | — | — |
skagarwal/google-places-api Version ^3.2 | — | — |
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.