libeo/lbo_vibeo
The AGPL-3.0 declaration, matching repository, and one runtime dependency make its shape clear. Organization backing helps, but security documentation and automated security scanning are absent.
61%
Total Score
83
100
88
75
Health Score Breakdown
The package has 24 releases over roughly four years, but none in the last 12 months. This is meaningful evidence of slowing maintenance, though the latest release is still present and the package is not deprecated.
There were no commits and no active maintainers in the last three months. Combined with the lack of releases in the last year, this points to weak current maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Thomas Lepage |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 typo3/cms-core Version ^13.4 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.