Purchase approval for Sylius 2 B2B company accounts: order and approval limits per member, pending orders held until a company approver approves them (no payment, shipment or invoice before), acknowledgement e-mail, expiry, shop, admin and API
62%
Total Score
caution
A brand-new release has no established commit history, relies on one maintainer, and uses unpinned workflow actions.
Only one registry account has publishing access. The linked project is user-owned rather than organization-owned, so there is limited visible publishing redundancy.
This is a brand-new package with 3 releases in less than 1 day, so there is not enough history to demonstrate sustained maintenance or release stability.
The repository reports 0 commits and 0 active maintainers in the last 3 months. Because the package is less than a day old, this is partly expected, but it leaves maintenance capacity unproven.
The repository has no published security policy, leaving the vulnerability reporting process unclear. This is a transparency gap, not evidence of unsafe code.
The single workflow was fully analyzed with no dangerous audit findings or untrusted checkout paths. However, both action references are unpinned, so their fetched code is not fixed to reviewed revisions.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sylius/sylius Version ^2.2.9 || ^2.3 | — | — |
tmonier/sylius-order-hold-plugin Version ^1.0 | — | — |
tmonier/sylius-company-accounts-plugin Version ^1.1 | — | — |
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.