The MIT license, focused dependency set, and included tests provide a sound baseline. Security documentation is absent and all three workflow actions are unpinned, adding maintenance and build-integrity concerns.
60%
Total Score
75
100
83
67
The package has only two releases, with the latest on January 23, 2023 and no releases in the last 12 months. This is a substantial maintenance concern, although the linked repository was pushed more recently.
The repository recorded zero commits and zero active maintainers in the last three months. The repository is not archived and was pushed on January 15, 2025, which partly offsets but does not remove the current inactivity concern.
The repository uses Make and Composer build tooling, indicating a reproducible project workflow. No security scanning tools were detected, which is a modest hygiene gap but not a severe dependency risk.
The repository has no security policy. This weakens disclosure transparency, but it is a hygiene concern rather than evidence that the release is unfit to use.
The single workflow was fully analyzed with no untrusted checkouts, script injection, or substantive audit findings. However, all three action references are unpinned, leaving the workflow exposed to upstream reference changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/customer Version ^6.0.0 || ^7.0.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.