The MIT license, focused dependency set, tests, and release notes make integration straightforward. The organization-backed repository is not archived, but recent commit activity is absent and no security policy is published.
62%
Total Score
75
100
86
50
The package has only two releases, with the latest in January 2020 and none in the last six years. This is a meaningful maintenance concern for a dependency, although the repository was pushed more recently.
There were no commits or active maintainers in the last three months. Combined with the old latest registry release, this indicates weak current maintenance momentum.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear. This lowers transparency but is not severe enough to make the release unfit on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/product Version ~6.7.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.