Five contributors shared recent work, and the repository is not archived. The missing security policy and partly unpinned workflow references leave modest transparency and build-reproducibility gaps.
73%
Total Score
100
75
50
The latest registry release is more than three years old, with no releases in the last 12 months. Recent repository commits partly compensate for the stale published cadence, but consumers may not receive current source changes.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest assurance gap rather than evidence of unsafe behavior.
The linked repository has no security policy, leaving vulnerability-reporting and response expectations less transparent for adopters.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/mail Version ^4.6.0 | — | — |
spryker/sales Version ^8.6.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/customer Version ^6.2.0 || ^7.0.0 | — | — |
spryker/transfer Version ^3.25.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.