lemon_framework/lemon
Tests, a README, a security policy, and a non-archived source repository provide useful transparency. The declared MIT license conflicts with the detected GPL-3.0 license, and both workflow action references are unpinned.
58%
Total Score
67
100
79
83
Health Score Breakdown
A LICENSE file is present, but the manifest declares MIT while the artifact license is detected as GPL-3.0. That mismatch should be resolved before relying on the package's licensing terms.
The package has existed for about 5 years with 63 releases, but only 1 release in the last 12 months despite a recent release, indicating a sharply slower cadence.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. Combined with only 1 release in the last year, this is a meaningful maintenance and abandonment concern.
There are 39 open issues, with no issues or pull requests opened or closed in the last month. This suggests limited current issue maintenance, though it is weaker evidence than the commit signal.
Composer is used for builds, but no security scanning tool was detected. This is a hygiene gap rather than evidence that the package is unsafe, especially given the repository's security policy.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Majkel |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^3.0 | — | — |
psr/container Version ^2.0 | — | — |
psr/simple-cache Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 months ago
- Created
- 5 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.