spryker/console
Healthy and suitable to depend on. It has a long release history, six releases in the last year, active contributions from seven maintainers, and complete package documentation and tests. The main caveat is limited repository security hygiene, including no security policy and no explicit workflow token permissions.
88%
Total Score
100
100
89
80
Health Score Breakdown
The repository has zero stars and one fork, which provides little community-adoption evidence. This is only a supporting concern because release and contributor activity are strong.
Composer build tooling is present, but no security scanning tools were detected. This leaves a security-process gap without indicating abandonment.
The repository has no SECURITY.md or other detected security policy, reducing transparency around vulnerability reporting and response.
The only workflow does not declare top-level token permissions. No write permissions were detected, but the missing explicit restriction is a workflow-hardening gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/config Version ^3.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/container Version ^1.4.0 | — | — |
spryker/application Version ^3.37.0 | — | — |
spryker/error-handler Version ^2.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 days ago
- Created
- 10 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.