spryker/application
Healthy and suitable to depend on. It has a long release history, regular recent releases, active work from five contributors, tests, and clear repository backing; the main caveat is limited repository security hygiene.
88%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and assurance gap, though it is not by itself evidence of abandonment or unsafe code.
The repository has no security policy. That makes vulnerability reporting and response expectations less transparent, although active releases and repository ownership provide some compensating maintenance evidence.
The CI workflow does not declare top-level token permissions. No write permissions were observed, but the missing explicit restriction leaves avoidable CI permission ambiguity.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/log Version ^3.1.0 | — | — |
spryker/twig Version ^3.13.0 | — | — |
spryker/config Version ^3.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/monolog Version ^2.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 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.