spryker/cms-collector
Healthy and usable, with a notable freshness caveat. The package has a clear repository, recent multi-contributor activity, release documentation, and no deprecation, but version 2.2.0 is over four years old and the repository lacks a security policy and explicit workflow permissions.
78%
Total Score
100
100
89
80
Health Score Breakdown
The package has 14 releases since 2017, but its latest registry release was over four years ago and there were no releases in the last 12 months. Recent repository activity partly compensates for the stale published version, but release freshness remains a real concern.
The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for a package intended for application integration.
The CI workflow does not declare top-level token permissions. No write permissions were observed, but explicit least-privilege configuration is absent.
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.2.0 || ^7.0.0 | — | — |
spryker/url Version ^3.0.0 | — | — |
spryker/store Version ^1.4.0 | — | — |
spryker/touch Version ^3.0.0 || ^4.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 9 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.