The package includes a README, changelog, stable version, and a matching organization-owned repository. Its only release was 489 days ago, with no commits or active maintainers in the last three months; the repository also lacks security scanning and pins none of four workflow actions.
62%
Total Score
75
86
50
This is the package's only release, published 489 days ago, with no releases in the last 12 months. That leaves maintenance and compatibility history too thin for a strong health assessment.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single-release history, this makes ongoing maintenance uncertain.
Composer build tooling is present, but no security-scanning tools were detected. That is a transparency and maintenance-hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This modestly reduces project transparency.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but all four action references are unpinned. The workflow also has no top-level permissions block, which is acceptable on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/store Version ^1.16.1 | — | — |
spryker/kernel Version ^3.75.0 | — | — |
spryker/propel-orm Version ^1.17.0 | — | — |
spryker/data-import Version ^1.3.0 | — | — |
spryker/util-encoding Version ^2.1.1 | — | — |
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.