@opentelemetry/exporter-trace-otlp-proto
OpenTelemetry Collector Exporter allows user to send collected traces to the OpenTelemetry Collector using protobuf over HTTP
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): This package predates widespread Sigstore provenance adoption on npm; no provenance is expected for this version range. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Package ships multiple build targets (CJS, ESM, ESNext), which naturally multiplies file count. Size growth is consistent with adding module formats, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects addition of ESM/ESNext build outputs for a multi-format package, not bundled payloads. Consistent with the package.json module fields. | ai | |
| phantom-deps | phantom-dep:protobufjs | AI (phantom-deps): protobufjs is used at runtime for .proto file loading, likely via dynamic require or delegated to sub-packages in the OTel monorepo architecture. | ai | |
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is a legitimate, widely-used protobuf library; its use is expected and appropriate for an OTLP protobuf exporter package. | ai | |
| phantom-deps | phantom-dep:@grpc/proto-loader | AI (phantom-deps): Dependency is used indirectly via OTel sub-packages; phantom detection is a false positive for this modular monorepo package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual maintainer (dyladan) to GitHub Actions CI/CD publishing with SLSA provenance; standard practice for OpenTelemetry project. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Same-org dependency likely used transitively or re-exported; standard for OpenTelemetry monorepo packages. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): Same-org dependency likely used transitively or re-exported; standard for OpenTelemetry monorepo packages. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.218.0 | 5 / 20 | |
| 0.217.0 | 5 / 20 | |
| 0.216.0 | 5 / 20 | |
| 0.215.0 | 5 / 20 | |
| 0.214.0 | 5 / 20 | |
| 0.213.0 | 5 / 20 | |
| 0.212.0 | 5 / 20 | |
| 0.211.0 | 5 / 20 | |
| 0.210.0 | 5 / 20 | |
| 0.209.0 | 5 / 20 | |
| 0.208.0 | 5 / 20 | |
| 0.207.0 | 5 / 20 | |
| 0.206.0 | 5 / 20 | |
| 0.205.0 | 5 / 21 | |
| 0.204.0 | 5 / 21 | |
| 0.203.0 | 5 / 22 | |
| 0.202.0 | 5 / 22 | |
| 0.201.1 | 5 / 22 | |
| 0.201.0 | 5 / 22 | |
| 0.200.0 | 5 / 22 | |
| 0.57.2 | 5 / 23 | |
| 0.57.1 | 5 / 23 | |
| 0.57.0 | 5 / 23 | |
| 0.56.0 | 5 / 23 | |
| 0.55.0 | 5 / 23 | |
| 0.54.2 | 5 / 23 | |
| 0.54.1 | 5 / 23 | |
| 0.54.0 | 5 / 23 | |
| 0.53.0 | 5 / 24 | |
| 0.52.1 | 5 / 25 | |
| 0.52.0 | 5 / 25 | |
| 0.51.1 | 6 / 26 | |
| 0.51.0 | 6 / 26 | |
| 0.50.0 | 6 / 26 | |
| 0.49.1 | 6 / 26 | |
| 0.49.0 | 6 / 26 | |
| 0.48.0 | 6 / 26 | |
| 0.47.0 | 6 / 25 | |
| 0.46.0 | 6 / 25 | |
| 0.45.1 | 6 / 25 | |
| 0.45.0 | 6 / 25 | |
| 0.44.0 | 6 / 25 | |
| 0.43.0 | 6 / 25 | |
| 0.42.0 | 6 / 25 | |
| 0.41.2 | 6 / 25 | |
| 0.41.1 | 6 / 25 | |
| 0.41.0 | 7 / 15 | |
| 0.40.0 | 6 / 13 | |
| 0.39.1 | 6 / 13 | |
| 0.39.0 | 6 / 13 | |
| 0.38.0 | 6 / 14 | |
| 0.37.0 | 6 / 14 | |
| 0.36.1 | 6 / 14 | |
| 0.36.0 | 6 / 14 | |
| 0.35.1 | 6 / 14 | |
| 0.35.0 | 6 / 14 | |
| 0.34.0 | 6 / 14 | |
| 0.33.0 | 7 / 14 | |
| 0.32.0 | 8 / 14 | |
| 0.31.0 | 8 / 14 | |
| 0.30.0 | 8 / 14 | |
| 0.29.2 | 8 / 14 | |
| 0.29.1 | 8 / 14 | |
| 0.29.0 | 8 / 14 | |
| 0.28.0 | 8 / 14 | |
| 0.27.0 | 6 / 14 |
v0.218.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.217.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.216.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.215.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.214.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.213.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.212.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.211.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.210.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.209.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.208.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.207.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.
v0.206.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-06. 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.
v0.205.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.204.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.203.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.202.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.201.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.201.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.200.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.57.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.57.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.57.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.56.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.55.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.54.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.54.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.54.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.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.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.
v0.41.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.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.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.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.