Tests, release notes, and a clear package repository support dependable maintenance. The workflow has two unpinned action references, and no security policy is published, but organization backing and recent repository activity reduce abandonment concerns.
78%
Total Score
100
100
88
75
The registry shows no releases in more than six years, which is a transparency and freshness concern for the published version. Recent repository activity partly offsets this by showing the project is still maintained.
Composer build tooling is present, but no security scanning tools were detected. This is a modest process gap rather than evidence of abandonment.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear for a package used in application integrations.
The single workflow was fully analyzed with no dangerous findings or excessive permissions, but two of four action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/search Version ^7.2.0 || ^8.0.0 | — | — |
spryker/product Version ^5.0.0 || ^6.0.0 | — | — |
spryker/cms-content-widget Version ^1.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.