sinemacula/laravel-route-linter
Clear licensing, documentation, repository tests, and release notes make the project easy to evaluate. Maintenance is concentrated in one contributor, while workflow credentials and action pinning need tighter controls.
68%
Total Score
83
100
89
75
Health Score Breakdown
All nine recent commits came from one contributor, giving the project a single-person maintenance dependency. Organization backing provides some handoff capacity, but no second active contributor is shown.
The repository has zero stars, forks, and watchers, so there is little public adoption evidence. Popularity is supporting evidence only and does not outweigh the active commits and releases.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and defensive-maintenance gap rather than evidence of abandonment.
All three workflows were analyzed with no untrusted checkouts or script injection, but all 10 action references are unpinned; two workflows grant top-level write access, and a high-confidence medium-severity secrets-inherit finding affects the release workflow. These create avoidable workflow supply-chain and credential-exposure concerns.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ben Carey |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/console Version * | — | — |
illuminate/routing Version * | — | — |
illuminate/support Version ^12.9 || ^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 3 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.