spryker/opentelemetry
Healthy and actively maintained, with solid release cadence, tests, and organization backing. The main caveats are missing security scanning and security-policy documentation, plus workflow permissions that are not explicitly restricted.
88%
Total Score
100
100
89
80
Health Score Breakdown
The repository has zero stars and one fork, which provides little external adoption evidence; however, popularity is supporting evidence and the package has active releases and organization backing.
Composer build tooling is present, but no security scanning tools were detected, leaving a genuine security-process gap.
The repository has no security policy, which weakens vulnerability-reporting transparency for a package intended for production instrumentation.
The CI workflow does not declare top-level token permissions. Although no write permissions were observed, the absence of an explicit restriction is a workflow-hardening gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Spryker |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/redis Version ^2.0.0 | — | — |
spryker/config Version ^3.0.0 | — | — |
spryker/guzzle Version ^2.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
monolog/monolog Version ^2.0.0 || ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 days ago
- Created
- 2 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.