spryker/company
Healthy and suitable to depend on. It has a long release history, recent releases, active contributions from five maintainers, and strong repository and packaging evidence; the main caveats are no security policy and incomplete workflow permission declarations.
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 process gap rather than evidence that the package is unsafe.
The repository has no SECURITY.md or equivalent security policy, leaving vulnerability reporting and response expectations undocumented.
The only workflow lacks top-level token permissions, so its CI access is not explicitly minimized; no workflow requests top-level write access.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/store Version ^1.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/propel-orm Version ^1.13.0 | — | — |
spryker/zed-request Version ^3.0.0 | — | — |
spryker/company-extension Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 days 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.