spryker/oauth-backend-api
Healthy and suitable to use, with active organizational maintenance and strong package transparency. The main caveats are no repository security policy or security-scanning tooling, and workflow permissions are not explicitly restricted.
86%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a genuine security-hygiene gap, though it does not by itself indicate abandonment.
No repository security policy was found. This weakens the project's transparency around vulnerability reporting and response.
The sole workflow has no top-level token permissions declaration, so its GitHub token access is not explicitly constrained to read-only permissions.
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.17.0 | — | — |
spryker/oauth Version ^2.4.0 | — | — |
spryker/kernel Version ^3.66.0 | — | — |
spryker/symfony Version ^3.5.0 | — | — |
spryker/transfer Version ^3.42.0 | — | — |
Weekly Downloads
Info
- Last Published
- 23 days ago
- Created
- 4 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.