Generelle Laravel-utviklingsprinsipper som publishable dokumentasjon.
78%
Total Score
100
100
89
75
The repository has zero stars, forks, and watchers, so there is little community validation. Because the package is only 196 days old and popularity is supporting evidence rather than a verdict, this is a minor concern rather than a major health risk.
The repository uses Composer build tooling, but no security scanning tools were detected. That weakens automated assurance even though other maintenance evidence is positive.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself indicate abandonment.
One workflow lacks top-level token permissions and another grants top-level write permissions. These settings are less restrictive than ideal and reduce workflow-security transparency, despite the absence of other dangerous workflow patterns.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.