flipjms/laravel-scenarios
Seven releases over nearly four years and no commits in the last three months suggest slow maintenance. A clear MIT license, release notes, repository tests, and matching source repository provide useful transparency, but the project remains a small one-person effort.
67%
Total Score
50
83
75
Health Score Breakdown
One registry maintainer is consistent with a small independently owned project, but it leaves little visible publishing redundancy if that person becomes unavailable.
The package has 7 releases over about 4 years, with 2 releases in the last 12 months and a median interval of about 10 months. This shows ongoing publishing but a slow cadence.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. The recent release provides some counterweight, but current development activity is limited.
The repository has 1 star, 2 forks, and 1 watcher. Popularity is only supporting evidence, but these low numbers provide little external evidence of broad adoption or review.
The repository has no security policy. This is a transparency and maintenance gap, though it does not by itself indicate that the release is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Filipe Santos |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nunomaduro/termwind Version ^2.0 | — | — |
illuminate/contracts Version ^9.0|^10.0|^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 4 years 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.