Tests, a clear MIT license, and a matching repository provide useful transparency. The small maintainer base and missing security policy leave limited resilience if maintenance stops.
62%
Total Score
63
100
88
75
Only one registry account has publishing access. The repository is user-owned rather than organization-backed, so there is little visible publishing redundancy if that maintainer becomes unavailable.
The registry namespace and repository owner match, but both identify a single user rather than an organization. This supports package identity while offering limited organizational continuity.
The package has only three releases since 2018, with no release in the last five years. Its stable version and non-deprecated status provide some continuity, but the long release gap raises abandonment concern.
There were no commits and no active maintainers in the last three months. Combined with no release for five years, this points to stalled maintenance.
The repository uses Composer and Make for build tasks, but no security scanning tooling was detected. The build setup is present, while security-process transparency is limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/process Version ^4.0 || ^5.0 | — | — |
symfony/event-dispatcher 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.