Organization backing and a matching repository add accountability, while the README and release notes make adoption easier. No security policy or scanning leaves less evidence of ongoing security practice.
62%
Total Score
75
86
50
The latest release was over a year ago, and there were no releases in the last 12 months. Six releases occurred overall, but the long current gap raises maintenance concern.
The repository had zero commits and zero active maintainers in the last three months. The repository is not archived, but this still provides weak evidence of current maintenance.
Composer is used for the build, which fits the package ecosystem. No security scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy. This does not make the package unfit, but it reduces transparency about how vulnerabilities are reported and handled.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.0 || ^2.0 || ^3.0 | — | — |
twig/twig Version ^3.0 | — | — |
symfony/lock Version ^6.4 || ^7.1 | — | — |
doctrine/dbal Version ^2.13 || ^3.0 | — | — |
symfony/config Version ^6.4 || ^7.1 | — | — |
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.