Multi-owner typed settings for Laravel applications
61%
Total Score
50
100
88
75
One registry publisher provides a thin publishing base, which limits resilience if that person becomes unavailable; the repository is also owned by an individual account, with no organizational backing shown.
Only two releases appeared across the package's 189-day history, with the latest release about six months ago. This provides limited evidence of sustained maintenance.
No commits and no active maintainers were recorded in the last three months, while the latest release was about six months ago. This is the strongest evidence of weakening maintenance momentum.
The repository uses Composer and Just for build tasks, but no security-scanning tooling was detected. That is a modest transparency and maintenance gap rather than a severe risk.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 8 action references are unpinned, leaving avoidable supply-chain drift.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cline/struct Version ^1.0.3 | — | — |
cline/morphism Version ^2.0.1 | — | — |
laravel/framework Version ^10.0 || ^11.0 || ^12.54.1 || ^13.0 | — | — |
cline/variable-keys Version ^2.0.2 | — | — |
facade/ignition-contracts Version ^1.0.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.