@opentelemetry/instrumentation-aws-sdk
OpenTelemetry instrumentation for `aws-sdk` and `@aws-sdk/client-*` clients for various AWS services
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 | publisher-changed | AI (provenance): Transition from individual maintainer to GitHub Actions CI/CD; expected for OpenTelemetry monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo release cadence; sub-package publish gaps are normal. | ai | |
| dependencies | unvetted-dep:@opentelemetry/propagation-utils | AI (dependencies): Part of the OpenTelemetry ecosystem; stable sibling package with no known issues. | ai |
Versions (showing 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 0.76.0 | 3 / 14 | |
| 0.75.0 | 3 / 14 | |
| 0.74.0 | 3 / 14 | |
| 0.73.0 | 3 / 14 | |
| 0.72.0 | 3 / 14 | |
| 0.71.0 | 3 / 14 | |
| 0.70.0 | 3 / 14 | |
| 0.69.0 | 3 / 14 | |
| 0.68.0 | 3 / 14 | |
| 0.67.0 | 3 / 14 | |
| 0.66.0 | 3 / 14 | |
| 0.65.0 | 3 / 14 | |
| 0.64.1 | 3 / 14 | |
| 0.64.0 | 3 / 24 | |
| 0.63.0 | 3 / 24 | |
| 0.62.0 | 3 / 25 | |
| 0.61.2 | 3 / 25 | |
| 0.61.1 | 3 / 25 | |
| 0.60.0 | 3 / 25 | |
| 0.59.0 | 3 / 25 | |
| 0.58.0 | 3 / 25 | |
| 0.57.0 | 4 / 23 | |
| 0.56.0 | 4 / 23 | |
| 0.55.0 | 4 / 23 | |
| 0.54.0 | 4 / 23 | |
| 0.53.0 | 4 / 23 | |
| 0.52.0 | 4 / 23 | |
| 0.51.0 | 4 / 23 | |
| 0.50.0 | 4 / 23 | |
| 0.49.1 | 4 / 23 | |
| 0.49.0 | 4 / 23 | |
| 0.48.0 | 4 / 23 | |
| 0.47.0 | 4 / 23 | |
| 0.46.0 | 4 / 23 | |
| 0.45.0 | 4 / 21 | |
| 0.44.0 | 4 / 23 | |
| 0.43.1 | 4 / 23 | |
| 0.43.0 | 4 / 23 | |
| 0.42.0 | 4 / 23 | |
| 0.41.0 | 4 / 23 | |
| 0.40.0 | 4 / 23 | |
| 0.39.1 | 4 / 23 | |
| 0.39.0 | 4 / 23 | |
| 0.38.1 | 4 / 23 | |
| 0.38.0 | 4 / 23 | |
| 0.37.2 | 4 / 23 | |
| 0.37.1 | 4 / 23 | |
| 0.37.0 | 4 / 23 | |
| 0.36.2 | 4 / 23 | |
| 0.36.1 | 4 / 23 | |
| 0.36.0 | 4 / 23 | |
| 0.35.0 | 5 / 23 | |
| 0.34.3 | 4 / 23 | |
| 0.34.2 | 4 / 23 | |
| 0.34.1 | 4 / 24 | |
| 0.34.0 | 4 / 24 | |
| 0.33.0 | 4 / 24 | |
| 0.32.0 | 4 / 24 | |
| 0.25.0 | 4 / 21 | |
| 0.10.0 | 4 / 24 | |
| 0.9.3 | 4 / 24 | |
| 0.9.2 | 4 / 24 | |
| 0.9.1 | 4 / 24 | |
| 0.9.0 | 4 / 24 | |
| 0.8.1 | 4 / 24 | |
| 0.8.0 | 4 / 24 | |
| 0.7.0 | 4 / 24 | |
| 0.6.0 | 4 / 23 | |
| 0.5.1 | 4 / 22 | |
| 0.5.0 | 4 / 22 | |
| 0.4.0 | 4 / 23 | |
| 0.3.1 | 4 / 23 | |
| 0.3.0 | 4 / 23 | |
| 0.2.0 | 4 / 23 | |
| 0.1.0 | 4 / 21 |
v0.76.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.75.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.51.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.50.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.49.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.49.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.48.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.47.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.46.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.45.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.44.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.43.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.43.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.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
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.2
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.