Order and customer timeline with internal staff notes for the Sylius 2 admin panel
68%
Total Score
caution
A brand-new first release with no established activity and fully unpinned workflow actions leaves meaningful maturity and build-hygiene concerns.
Only one registry account can publish releases. That is a modest continuity risk for an individually owned project, with no organization backing shown to compensate for the narrow publishing base.
The repository is owned by an individual user rather than an organization, so the single registry maintainer represents a genuinely narrow project backing base.
This is the package's first release and it is 0 days old, so there is no demonstrated release cadence or long-term maintenance history yet.
There were 0 commits and 0 active maintainers in the preceding 3 months, but the project is 0 days old and was pushed recently, so this is mainly an absence of history rather than evidence of abandonment.
No repository security policy was found. For a new package this is a transparency gap, though it does not by itself indicate unsafe code or abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sylius/sylius Version ^2.2 | — | — |
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.