spryker-shop/cms-page
The README, changelog, and release notes provide enough guidance for adoption. The organization-backed project has a broad active contributor base; workflow pinning and missing security documentation are the main remaining limitations.
84%
Total Score
100
93
75
Health Score Breakdown
Composer build tooling is present, but no security-scanning tools were detected. That weakens automated assurance somewhat, though it does not by itself indicate abandonment or unsafe behavior.
The repository has no security policy, leaving vulnerability-reporting expectations and response guidance undocumented. This is a transparency gap, but active maintenance and organization backing partly reduce its practical impact.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/cms Version ^6.4.0 || ^7.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/locale Version ^3.8.0 || ^4.0.0 | — | — |
spryker/symfony Version ^3.5.0 | — | — |
spryker/customer Version ^7.4.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.