B2B company accounts for Sylius 2: companies with members and roles (admin, buyer, approver), company area in the customer account (members, company orders), admin CRUD, shop and admin API, voters, events, and an optional account owner bridge for the order-hold kernel
70%
Total Score
caution
Only two releases exist so far, and the workflow uses two unpinned actions.
The repository is owned by an individual account rather than an organization, so there is no demonstrated organizational backing to offset the single-person project context.
Only two releases exist and the package is less than one day old, so there is little evidence of an established release or maintenance history.
The repository reports zero commits and zero active maintainers in the last three months; because the package is newly created, this is limited history rather than clear abandonment, but it leaves maintenance capacity unproven.
No repository security policy was found, leaving vulnerability-reporting guidance unclear for a package with limited operating history.
The workflow audit completed cleanly with no untrusted checkout, injection, or high-severity findings, but both analyzed action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sylius/sylius Version ^2.2.9 || ^2.3 | — | — |
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.