spryker/glossary
The module has a long release history, recent commits from six contributors, and substantial tests and documentation. Its workflow has two unpinned actions and the repository lacks a security policy, so maintenance hygiene is not flawless.
88%
Total Score
100
100
94
75
Health Score Breakdown
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning layer is a modest transparency and hygiene gap, not evidence of abandonment.
The repository has no security policy file. This weakens the documented process for reporting and handling vulnerabilities, though active commits and organization backing partly compensate for the gap.
The single workflow was fully analyzed with no failed files, dangerous triggers, untrusted checkouts, script injection, or audit findings. However, 2 of 4 action references are unpinned, leaving a minor reproducibility and supply-chain hygiene 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/gui Version ^3.0.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/touch Version ^3.0.0 || ^4.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/storage Version ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 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.