spryker/oauth-client
Tests, changelog, release notes, and a clear package-matched repository support dependable maintenance. Workflow references are only partly pinned and the repository has no security policy, but no dangerous workflow findings were reported.
82%
Total Score
100
100
88
75
Health Score Breakdown
The package has seven releases over about four years, but none in the last 12 months. This slows confidence in registry delivery, although five recent repository commits show ongoing project activity.
The repository uses Composer build tooling, but no security-scanning tool was detected. This is a modest transparency gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. Other maintenance and packaging evidence partly offsets this documentation gap.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, a minor reproducibility concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/kernel Version ^3.30.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/payment-extension Version ^1.1.0 | — | — |
spryker/kernel-app-extension Version ^1.0.0 | — | — |
spryker/oauth-client-extension Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.