spryker/user
Healthy and suitable to depend on. It has a long release history, a release within the last day, regular recent activity from seven contributors, complete package documentation and tests, and clear organization backing. The main gaps are missing security-policy and explicit workflow token-permission settings.
88%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tooling was detected, leaving a modest transparency and assurance gap.
The repository has no security policy file, so vulnerability-reporting guidance is less transparent despite the package's otherwise active maintenance.
The one workflow does not declare top-level token permissions. No write permissions were observed, but explicit least-privilege settings would provide stronger workflow hygiene.
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.33.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/kernel Version ^3.76.0 | — | — |
spryker/session Version ^3.3.0 || ^4.14.0 | — | — |
spryker/symfony Version ^3.21.0 | — | — |
spryker/transfer Version ^3.27.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.