zipkin-transport-http
Transports Zipkin trace data via HTTP
1
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
openzipkin
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): OpenZipkin intentionally publishes a suite of consistently-named packages (zipkin-transport-*, zipkin-instrumentation-*); templated naming is expected for this ecosystem, not a spam indicator. | ai | |
| dependencies | unvetted-dep:zipkin | AI (dependencies): zipkin is a sibling package in the same openzipkin/zipkin-js monorepo, published by the same organization. Legitimate internal dependency. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.22.0 | 1 / 3 |
v0.22.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.