It has a clear MIT license, tests, and a repository that matches the package and is owned by an organization. The workflow leaves all three actions unpinned and the repository has no security policy.
58%
Total Score
83
100
75
50
Only two releases were published, both in September 2023, with no release in about three years. This is substantial evidence of limited ongoing maintenance, though the package may be intentionally stable.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but current maintenance capacity is not demonstrated.
The repository uses Make and Composer, showing basic build tooling, but no security-scanning tools were detected. This is a modest transparency and maintenance gap.
The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, although it is not by itself evidence of unsafe code.
The workflow audit completed cleanly with no dangerous triggers, untrusted checkouts, or audit findings. However, all three action references are unpinned, weakening build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/checkout-rest-api Version ^3.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.