A single maintainer, no security scanning, and no license file reduce confidence in long-term support and reuse. The README and matching repository help consumers understand it, but the extended inactivity leaves compatibility uncertain.
38%
Total Score
25
100
63
100
Neither the package metadata nor the artifact or repository contains a recognized license. That creates a material adoption and redistribution risk for an open-source dependency.
The latest release was over 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility updates.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and indicating no current maintenance capacity.
Only one registry publishing maintainer is listed. The organization-backed repository partly offsets this thin registry presence, but it does not demonstrate active maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and hygiene gap, especially alongside the absence of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
knplabs/knp-menu-bundle Version ~2 | — | — |
knplabs/knp-markdown-bundle Version ~1.3 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.