@opentelemetry/otlp-grpc-exporter-base
OpenTelemetry OTLP-gRPC Exporter base (for internal use only)
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase is explained by bundling compiled protobuf definitions alongside the new protobufjs runtime dependency, consistent with the package's gRPC exporter purpose. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): pichlermarc is a well-established OpenTelemetry contributor with 428 approved packages and 0 rejections; this is a legitimate project maintainer transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): protobufjs is a well-known library and its addition is expected for a gRPC exporter that generates and uses protobuf definitions. | ai | |
| provenance | publisher-changed | AI (provenance): OpenTelemetry JS monorepo migrated to GitHub Actions CI/CD publishing; SLSA provenance attestation confirms legitimate automated publishing pipeline. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal is consistent with the project's transition to GitHub Actions-based automated publishing; package remains under the official open-telemetry org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo release cadence changes for this experimental package, not account takeover. SLSA provenance and consistent package metadata confirm legitimacy. | ai | |
| provenance | slsa-provenance | AI (provenance): Official OpenTelemetry JS monorepo package published via GitHub Actions with Sigstore SLSA attestation; this is expected and stable for all versions. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 0.218.0 | 4 / 11 | |
| 0.217.0 | 4 / 11 | |
| 0.216.0 | 4 / 11 | |
| 0.215.0 | 4 / 11 | |
| 0.214.0 | 4 / 11 | |
| 0.213.0 | 4 / 11 | |
| 0.212.0 | 4 / 11 | |
| 0.211.0 | 4 / 11 | |
| 0.210.0 | 4 / 11 | |
| 0.209.0 | 4 / 11 | |
| 0.208.0 | 4 / 11 | |
| 0.207.0 | 4 / 11 | |
| 0.206.0 | 4 / 11 | |
| 0.205.0 | 4 / 12 | |
| 0.204.0 | 4 / 12 | |
| 0.203.0 | 4 / 13 | |
| 0.202.0 | 4 / 13 | |
| 0.201.1 | 4 / 13 | |
| 0.201.0 | 4 / 13 | |
| 0.200.0 | 4 / 13 | |
| 0.57.2 | 4 / 13 | |
| 0.57.1 | 4 / 13 | |
| 0.57.0 | 4 / 13 | |
| 0.56.0 | 4 / 13 | |
| 0.55.0 | 4 / 13 | |
| 0.54.2 | 4 / 13 | |
| 0.54.1 | 4 / 13 | |
| 0.54.0 | 4 / 13 | |
| 0.53.0 | 4 / 14 | |
| 0.52.1 | 4 / 15 | |
| 0.52.0 | 4 / 15 | |
| 0.51.1 | 4 / 18 | |
| 0.51.0 | 4 / 18 | |
| 0.50.0 | 4 / 18 | |
| 0.49.1 | 4 / 18 | |
| 0.49.0 | 4 / 18 | |
| 0.48.0 | 4 / 18 | |
| 0.47.0 | 4 / 19 | |
| 0.46.0 | 4 / 19 | |
| 0.45.1 | 4 / 19 | |
| 0.45.0 | 4 / 19 | |
| 0.44.0 | 4 / 19 | |
| 0.43.0 | 4 / 19 | |
| 0.42.0 | 4 / 19 | |
| 0.41.2 | 4 / 19 | |
| 0.41.1 | 4 / 19 | |
| 0.41.0 | 5 / 19 | |
| 0.40.0 | 4 / 17 | |
| 0.39.1 | 4 / 17 | |
| 0.39.0 | 4 / 17 | |
| 0.38.0 | 4 / 17 |
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.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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
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-09-12. This could indicate a legitimate maintainer transition or an account compromise.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.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-07-06. This could indicate a legitimate maintainer transition or an account compromise.
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.