spryker/warehouse-oauth-backend-api
Healthy and suitable to depend on. The repository is active, has balanced recent contributions, tests, release notes, and clear package ownership; the main caveats are infrequent releases and limited repository security controls.
84%
Total Score
100
100
88
80
Health Score Breakdown
The package has existed for more than three years and has a recent release, but only one release in the last 12 months and a median interval of about 288 days indicate a slow release cadence.
The repository uses Composer for builds, but no security scanning tools were detected, leaving a modest transparency and preventative-maintenance gap.
The repository has no security policy, which makes vulnerability reporting and disclosure expectations less clear for users of this authentication-related module.
The only workflow lacks a top-level GitHub Actions permissions declaration. No write permissions were observed, but explicitly restricting token permissions would provide stronger CI 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/log Version ^3.17.0 | — | — |
spryker/oauth Version ^2.4.0 | — | — |
spryker/kernel Version ^3.66.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.42.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 3 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.