It is clearly licensed, documented, and published from a matching repository. The missing security policy and scanning leave less assurance for a package handling calendar integrations.
58%
Total Score
50
100
88
83
The repository is owned by an individual account rather than an organization, so there is no organizational backing signal to offset the thin maintenance evidence.
The latest release was published in August 2021, more than five years ago, with no releases in the last 12 months. This is substantial evidence of stalled maintenance despite the package having eight historical releases.
There were no commits and no active maintainers in the last three months. This weakens confidence that the package is receiving ongoing maintenance, even though the repository is not archived.
The repository uses Composer for builds, but no security-scanning tools were detected. That is a modest transparency and maintenance gap rather than a severe risk.
No security policy was found in the repository, leaving the process for reporting and handling vulnerabilities unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/laravel-google-calendar Version ^3.1.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.