The organization-backed repository matches the package and documents this version with release notes. There is no security policy or automated security scanning, so ongoing oversight is limited.
58%
Total Score
100
67
50
The package has only two releases, with the latest published about seven years ago and none in the last 12 months. This indicates materially stale maintenance despite the package not being deprecated.
Composer build tooling is present, but no security-scanning tool is configured. That leaves security checks less visible and systematic than they could be.
The repository is not archived, which preserves a path for maintenance, but it was last pushed about six years ago. The long inactivity still raises abandonment risk.
The linked repository has no security policy. This weakens vulnerability-reporting transparency, although it is a maintenance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker-feature/shipment Version ~2018.12.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.