Risky to adopt: the last release and repository push were over eight years ago, with no recent commits or issue activity. It remains a real, licensed package with tests, a README, and organization backing, but its long inactivity makes ongoing compatibility and maintenance uncertain.
38%
Total Score
50
71
75
The package has 52 releases since 2014, but its latest release was over eight years ago and it had no releases in the last 12 months. This is strong evidence of abandonment risk despite its historically regular release cadence.
The repository had zero commits and zero active maintainers in the last three months. This is the clearest maintenance concern and indicates that fixes or compatibility updates are unlikely to arrive promptly.
There were no new or closed issues and no pull-request activity in the measured one-month period, with seven issues still open. Combined with the old last release, this points to an inactive project.
Composer and Phing build tooling are present, showing some project structure, but no security-scanning tools were detected. That is a transparency and maintenance gap for a package with no recent development activity.
The repository is not marked archived, which is better than an explicitly discontinued project. However, its last push was over eight years ago, so the unarchived status does not demonstrate active maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
avisota/core Version ^1.2 | — | — |
contao/core-bundle Version ^3.5.5 | — | — |
bit3/string-builder Version ^2.0 | — | — |
symfony/http-foundation Version ^2.7 | — | — |
contaoblackforest/contao-logger Version ^2.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.