@opentelemetry/exporter-zipkin
OpenTelemetry Zipkin Exporter allows the user to send collected traces to Zipkin.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opentelemetry/base | AI (phantom-deps): Monorepo dependency management pattern; same-org scope dependencies declared for version control. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): Monorepo dependency management pattern; same-org scope dependencies declared for version control. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/tracing | AI (phantom-deps): Monorepo dependency management pattern; same-org scope dependencies declared for version control. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/types | AI (phantom-deps): Monorepo dependency management pattern; same-org scope dependencies declared for version control. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal accompanies transition to automated CI/CD publishing; consistent with OpenTelemetry org-level supply chain hardening. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): @opentelemetry/resources is a declared runtime dependency in package.json from the same org; phantom-dep firing is a false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publishing with SLSA provenance is a supply chain improvement for this established OpenTelemetry monorepo package; generalizes to future versions. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 2.7.1 | 4 / 23 | |
| 2.7.0 | 4 / 23 | |
| 2.6.1 | 4 / 23 | |
| 2.6.0 | 4 / 23 | |
| 2.5.1 | 4 / 23 | |
| 2.5.0 | 4 / 23 | |
| 2.4.0 | 4 / 23 | |
| 2.3.0 | 4 / 23 | |
| 2.2.0 | 4 / 23 | |
| 2.1.0 | 4 / 24 | |
| 2.0.1 | 4 / 25 | |
| 2.0.0 | 4 / 25 | |
| 1.30.1 | 4 / 26 | |
| 1.30.0 | 4 / 26 | |
| 1.29.0 | 4 / 26 | |
| 1.28.0 | 4 / 26 | |
| 1.27.0 | 4 / 26 | |
| 1.26.0 | 4 / 27 | |
| 1.25.1 | 4 / 28 | |
| 1.25.0 | 4 / 28 | |
| 1.24.1 | 4 / 28 | |
| 1.24.0 | 4 / 28 | |
| 1.23.0 | 4 / 28 | |
| 1.22.0 | 4 / 28 | |
| 1.21.0 | 4 / 28 | |
| 1.20.0 | 4 / 27 | |
| 1.19.0 | 4 / 27 | |
| 1.18.1 | 4 / 27 | |
| 1.18.0 | 4 / 27 | |
| 1.17.1 | 4 / 27 | |
| 1.17.0 | 4 / 27 | |
| 1.16.0 | 4 / 27 | |
| 1.15.2 | 4 / 27 | |
| 1.15.1 | 4 / 27 | |
| 1.15.0 | 5 / 27 | |
| 1.14.0 | 4 / 25 | |
| 1.13.0 | 4 / 25 | |
| 1.12.0 | 4 / 26 | |
| 1.11.0 | 4 / 26 | |
| 1.10.1 | 4 / 26 | |
| 1.10.0 | 4 / 26 | |
| 1.9.1 | 4 / 26 | |
| 1.9.0 | 4 / 26 | |
| 1.8.0 | 4 / 26 | |
| 1.7.0 | 4 / 26 | |
| 1.6.0 | 4 / 26 | |
| 1.5.0 | 4 / 26 | |
| 1.4.0 | 4 / 26 | |
| 1.3.1 | 4 / 26 | |
| 1.3.0 | 4 / 26 | |
| 1.2.0 | 4 / 26 | |
| 1.1.1 | 4 / 26 | |
| 1.1.0 | 4 / 26 | |
| 1.0.1 | 4 / 26 | |
| 1.0.0 | 4 / 26 | |
| 0.26.0 | 4 / 26 | |
| 0.25.0 | 4 / 26 | |
| 0.24.0 | 4 / 26 | |
| 0.23.0 | 4 / 27 | |
| 0.22.0 | 4 / 27 | |
| 0.21.0 | 4 / 27 | |
| 0.20.0 | 4 / 27 | |
| 0.19.0 | 3 / 28 | |
| 0.18.2 | 4 / 27 | |
| 0.18.1 | 4 / 27 | |
| 0.18.0 | 4 / 27 | |
| 0.17.0 | 4 / 27 | |
| 0.16.0 | 4 / 27 | |
| 0.15.0 | 4 / 27 | |
| 0.14.0 | 4 / 27 | |
| 0.13.0 | 4 / 27 | |
| 0.12.0 | 4 / 27 | |
| 0.11.0 | 4 / 11 | |
| 0.10.2 | 4 / 11 | |
| 0.10.1 | 4 / 11 | |
| 0.10.0 | 4 / 11 | |
| 0.9.0 | 4 / 11 | |
| 0.8.3 | 4 / 11 | |
| 0.8.2 | 4 / 11 | |
| 0.8.1 | 4 / 13 | |
| 0.8.0 | 4 / 13 | |
| 0.7.0 | 5 / 13 | |
| 0.6.1 | 5 / 14 | |
| 0.6.0 | 5 / 14 | |
| 0.5.2 | 5 / 14 | |
| 0.5.1 | 5 / 14 | |
| 0.5.0 | 5 / 14 | |
| 0.4.0 | 4 / 14 | |
| 0.3.3 | 4 / 14 | |
| 0.3.2 | 4 / 14 | |
| 0.3.1 | 4 / 14 | |
| 0.3.0 | 4 / 14 | |
| 0.2.0 | 4 / 14 | |
| 0.1.1 | 4 / 14 | |
| 0.1.0 | 4 / 14 |
v2.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.30.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.27.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-23. This could indicate a legitimate maintainer transition or an account compromise.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-08. This could indicate a legitimate maintainer transition or an account compromise.
v1.15.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-07-24. This could indicate a legitimate maintainer transition or an account compromise.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-06. This could indicate a legitimate maintainer transition or an account compromise.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.