The repository has recent commits from two contributors, a README, changelog, tests, and a clear license. Workflow actions are all unpinned and the project has no security policy, so maintenance is stronger than its security hygiene.
78%
Total Score
83
100
94
75
The registry namespace and repository are owned by the same individual account, so there is no organizational handoff buffer. This is partly offset by two recent contributors and current release activity.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a modest transparency gap rather than evidence of abandonment.
The repository has no security policy. For a Laravel package that handles OAuth tokens and weather-service credentials, this weakens vulnerability-reporting transparency.
The single workflow was fully analyzed with no untrusted checkouts, script injection, or audit findings, but all 7 action references are unpinned. That leaves avoidable workflow supply-chain exposure despite otherwise clean workflow hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.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.