The alpha release needs more validation before production use, and recent repository activity is quiet. Licensing, release notes, repository tests, and a non-archived organization-backed project provide useful support.
61%
Total Score
67
86
67
The repository recorded 0 commits and 0 active maintainers in the last three months. This is a meaningful maintenance concern, although the assessed release was published recently and the repository is not archived.
There were 5 open issues and no new or closed issues, pull requests, or merges in the last month. That shows limited recent project interaction, but does not by itself demonstrate abandonment.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and hygiene gap rather than evidence that the release is unsafe.
The linked repository has no security policy. That weakens vulnerability-reporting transparency, although it does not establish a maintenance failure on its own.
This release is v3.0.0-alpha.2, so it is explicitly a prerelease rather than a stable major release. The recent prerelease share is only 0.1, which partly limits the concern but does not remove alpha-version risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.1 || ^2.0 || ^3.0 | — | — |
twig/twig Version ^3.0 | — | — |
league/uri Version ^6.0 || ^7.5 | — | — |
symfony/form Version ^6.4 || ^7.1 | — | — |
sylius/channel Version ^2.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.