Usable with caveats: the package is licensed, documented, stable, and backed by an organization, but it has had no registry release in nearly six years and no commits in the last three months. Verify that the linked repository is genuinely the source before adopting it.
52%
Total Score
75
100
72
75
The package has 21 releases over nearly ten years, but the latest release was nearly six years ago and there were no releases in the last 12 months. This is a meaningful maintenance concern for a dependency.
There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates little current maintenance capacity.
The repository name does not match the package name and its README does not mention the package. Although name differences can occur in related repositories, this combination raises concern that the linked source may not directly correspond to the published package.
The repository has no stars and one fork, offering little community adoption evidence. Popularity is supporting evidence rather than a decisive health measure, so this is only a modest concern.
The repository uses Make and Composer, but no security scanning tools are present. The missing scanning is a transparency and maintenance gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^2.0 | — | — |
sidus/base-bundle Version ^1.0 | — | — |
cleverage/filter-bundle Version ^3.1 | — | — |
sensio/framework-extra-bundle Version ^5.0 | — | — |
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.