spryker/security-oauth-user
Healthy and suitable to use. It has regular recent releases, active work from six contributors, complete package and repository structure, and no deprecation or archive warning; the main caveats are missing security-policy documentation and undeclared workflow token permissions.
86%
Total Score
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no SECURITY.md or equivalent security policy, leaving vulnerability reporting and response expectations undocumented.
The CI workflow has no top-level token-permissions declaration. Although no write permissions were detected, explicitly restricting permissions 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/acl Version ^3.4.0 | — | — |
spryker/user Version ^3.17.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.5.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 days ago
- Created
- 5 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.