spryker/customers-rest-api
Healthy and suitable to depend on. It has eight years of releases, twelve releases in the last year, recent activity from six contributors, and complete package tests and documentation; the main caveats are limited repository security hygiene and unspecified workflow token permissions.
90%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tools were detected. This is a hygiene gap, though it is not evidence of abandonment by itself.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not a severe dependency-health risk on its own.
The one workflow does not declare top-level token permissions. No write permissions were observed, but the unspecified default is weaker 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/kernel Version ^3.30.0 | — | — |
spryker/session Version ^3.2.0 || ^4.0.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/customer Version ^7.82.0 | — | — |
spryker/transfer Version ^3.42.0 | — | — |
Weekly Downloads
Info
- Last Published
- 11 days ago
- Created
- 8 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.