The package has no recent commits or releases, and its repository does not clearly identify the package. MIT licensing, an active non-archived organization-owned repository, and a clean dependency installation profile provide useful safeguards.
58%
Total Score
75
75
83
The package has 44 releases since August 2018, but none in the last 12 months; its latest release was about 14 months ago. This indicates a meaningful maintenance slowdown despite the long release history.
The repository had zero commits and zero active maintainers in the last 3 months. Together with no registry releases in the last year, this raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. This leaves uncertainty about whether the linked repository is the actual source rather than a broader or unrelated project.
The repository uses Composer, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is a secondary concern compared with the maintenance signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^2.5|^3.0 | — | — |
symfony/form Version ^4.0|^5.0 | — | — |
symfony/validator Version ^4.0|^5.0 | — | — |
doctrine/annotations Version ^1.6 | — | — |
symfony/security-bundle Version ^4.0|^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.