Release cadence is sparse, and the small single-owner project has no security policy or pinned workflow actions. Clear documentation, repository tests, release notes, MIT licensing, and a recent stable release provide useful reassurance.
68%
Total Score
50
100
94
67
The registry namespace and repository are owned by the same individual account, so the package has clear ownership but no organizational backing shown by the provided evidence. This leaves a relatively narrow continuity base.
The package has existed since 2016 with 20 releases, but only one release in the last 12 months. That indicates a slower maintenance pace rather than abandonment, especially given the recent release.
The repository had zero commits and zero active maintainers in the last three months. The recent release partly offsets this, but the current maintenance capacity remains uncertain.
No security policy is present in the repository. For a bundle integrated into application request handling, this is a transparency gap, though it is not evidence of an unsafe release by itself.
Both workflows were analyzed without high-confidence findings or dangerous triggers, but all six action references are unpinned. Missing top-level permissions blocks are acceptable on their own; unpinned actions remain a workflow hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/lock Version ^6.4 || ^7.4 | — | — |
symfony/config Version ^6.4 || ^7.4 | — | — |
symfony/http-kernel Version ^6.4 || ^7.4 | — | — |
symfony/http-foundation Version ^6.4 || ^7.4 | — | — |
symfony/event-dispatcher Version ^6.4 || ^7.4 | — | — |
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.