The MIT license, clear package structure, and readme make adoption easier. Single-person ownership and a small community leave less maintenance capacity if development slows.
68%
Total Score
50
94
67
One registry maintainer is responsible for publishing, leaving limited visible publishing redundancy; the active release history partly offsets this concern.
Composer is used for builds, but no security scanning tooling is present, leaving a modest transparency and maintenance gap.
The repository has no security policy, so there is no documented process for reporting and handling vulnerabilities.
The single workflow was fully analyzed with no dangerous sinks or audit findings, but all 6 action references are unpinned, weakening build reproducibility and update control.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/process Version ^3.4 || ^4.4 || ^5.4 || ^6.0 || ^7.0 || ^8.0 | — | — |
symfony/routing Version ^3.4 || ^4.4 || ^5.4 || ^6.0 || ^7.0 || ^8.0 | — | — |
symfony/http-foundation Version ^3.4 || ^4.4 || ^5.4 || ^6.0 || ^7.0 || ^8.0 | — | — |
symfony/framework-bundle Version ^3.4 || ^4.4 || ^5.4 || ^6.0 || ^7.0 || ^8.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.