j4kim/lfta
Tests, a README, and a declared MIT license provide useful basics, and five runtime dependencies are reasonable for a Laravel starter. The repository has no commit activity yet, and the package is only about an hour old; no security policy or scanning is present.
58%
Total Score
50
100
88
50
Health Score Breakdown
Several Composer lifecycle scripts run during installation or updates, including post-create-project-cmd. These are expected for a Laravel project template but increase the amount of code executed automatically.
The package is 0 days old with only two releases, published about 1 hour and 8 minutes apart. This is too little history to establish maintenance reliability.
The repository has 0 commits in the last 3 months and 0 active maintainers. Because the project is newly published, this is an early maintenance concern rather than proof of abandonment.
Composer build tooling is present, but no security scanning tools are reported. This leaves an avoidable transparency gap for a package intended to seed applications.
The repository has no security policy. That weakens disclosure transparency, although it does not by itself show that the code is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/tinker Version ^3.0 | — | — |
laravel/sanctum Version ^4.0 | — | — |
filament/filament Version ^5.0 | — | — |
laravel/framework Version ^13.8 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 2 days 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.