leafs/mvc
The MIT license, README, and release notes make adoption clearer. Limited security tooling and a single recent contributor add maintenance risk, while organization backing provides some continuity.
76%
Total Score
88
100
94
67
Health Score Breakdown
The package uses post-create-project-cmd and post-root-package-install scripts. These are expected for a framework application scaffold, but they add install-time behavior that should be understood before adoption.
All 8 commits in the last 3 months came from one contributor, creating a concentrated maintenance dependency. Organization ownership provides some ability to hand work off, but no second recent contributor is shown.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning reduces supply-chain hygiene, though it is not evidence of unsafe code by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 leafs/leaf Version ^5.0 | — | — |
leafs/blade Version ^5.0 | — | — |
leafs/logger Version ^5.0 | — | — |
leafs/schema Version ^5.0 | — | — |
leafs/mvc-core Version ^5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 6 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.