The repository has no security policy or security scanning, reducing transparency. Organization ownership, a clear README, a license, and release notes provide useful context, but do not offset the stale maintenance picture.
58%
Total Score
75
83
75
The package has only two releases, both published about 1 year 3 months ago, with no releases in the last 12 months. This indicates a thin and currently inactive release history.
There were zero commits and zero active maintainers in the last three months, consistent with no repository activity for about 1 year 3 months. This is a meaningful maintenance and abandonment concern.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the complete absence of observed adoption adds a modest maturity concern.
Composer build tooling is present, but no security scanning tools were detected. For a plugin handling shipping integrations, that is a transparency and maintenance gap.
The repository has no security policy. This weakens the project's disclosure and maintenance transparency, although it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
sylius/sylius Version ~1.11.0 || ~1.12.0 || ~1.13.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.