Clear documentation, tests in the repository, release notes, and a matching source repository improve transparency. Maintenance has been inactive for about nine months, with one registry maintainer, no security scanning, and all three workflow actions unpinned.
62%
Total Score
67
88
83
One registry maintainer is a thin publishing base, although the linked repository is owned by the same individual, so this is a capacity concern rather than a mismatch.
The package has only two releases, both within eight days, and no release activity for about nine months despite being 276 days old. This leaves limited evidence of sustained maintenance.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the last release. That raises abandonment risk for a young package.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The workflow has no untrusted trigger or audit finding, but all 3 of 3 action references are unpinned, so they can change without a repository commit. The missing top-level permissions block is common and not a concern by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/config Version ^7.1 | — | — |
symfony/validator Version ^7.1 | — | — |
symfony/http-kernel Version ^7.1 | — | — |
symfony/twig-bundle Version ^7.1 | — | — |
symfony/security-core Version ^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.