The package includes a full test suite, a clear MIT license, and organization-backed source code. Its workflow uses three unpinned actions, and the repository lacks a security policy, adding maintenance and build-integrity concerns.
58%
Total Score
75
86
50
The package has only one release, published about three and a half years ago, with no releases in the last 12 months. This is a substantial maintenance concern despite the stable 1.0.0 version.
The repository recorded no commits and no active maintainers in the last three months. Combined with the single-release history, this increases the risk that maintenance has slowed or stopped.
The repository uses Make and Composer build tooling, but no security-scanning tools were detected. The established build tooling helps reproducibility, while the missing scanning is a modest hygiene gap.
No security policy was found in the repository. This reduces transparency for reporting and handling vulnerabilities, though it is not by itself evidence that the package is unsafe.
The workflow audit completed successfully with no dangerous triggers or audit findings, but all three referenced actions are unpinned. That leaves build inputs less reproducible and warrants a modest caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/customer Version ^7.0.0 | — | — |
spryker/product-list Version ^1.0.0 | — | — |
spryker/business-on-behalf Version ^1.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.