Tests and licensing are present, and the repository is not archived. The old release cadence, no recent commits, missing security policy, and unpinned workflow actions add maintenance and build-integrity concerns.
58%
Total Score
75
100
88
75
The package has had only two releases, with the latest on January 23, 2023 and none in the last 12 months. This is a meaningful maintenance concern, although the repository was pushed more recently.
There were zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last 12 months, this raises abandonment risk.
The project uses Make and Composer, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified.
All three analyzed workflow action references are unpinned, so workflow behavior can change when upstream references move. The audit was complete and found no untrusted checkout, script injection, or high-confidence security findings.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/product-list Version ^1.0.0 | — | — |
fond-of-spryker/brand-product Version dev-spryker_upgrade | — | — |
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.