The package includes tests, a matching MIT license, and is backed by an organization-owned repository. Its workflow leaves all three action references unpinned, and no security scanning or policy is present.
62%
Total Score
75
88
67
Only two releases exist, with the latest published more than three years ago and none in the last 12 months. This is a substantial maintenance concern for a dependency, although the repository is not archived.
There were no commits and no active maintainers in the last three months. This reinforces the stale release history and raises abandonment risk.
The repository uses Make and Composer, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of unsafe code.
No repository security policy was found. This limits transparency around vulnerability reporting but is not severe enough to make the package unfit by itself.
The single workflow was fully analyzed with no reported audit findings or untrusted execution sinks, but all three action references are unpinned. The workflow has no top-level permissions block, which is acceptable on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/product Version ^5.0.0 || ^6.0.0 | — | — |
fond-of-oryx/cart-code-type Version ^1.0.0 || ^2.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.