← Home

@opentelemetry/propagator-aws-xray-lambda

npm Repository Homepage

OpenTelemetry AWS Xray propagator provides context propagation for systems that are using AWS X-Ray format.

12
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dyladanpichlermarc

Keywords

opentelemetrynodejstracingawsxray

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): opentelemetry-js-contrib migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate automated release pipeline. ai

Versions (showing 12 of 12)

Version Deps Published
0.56.0 1 / 1
0.55.4 1 / 1
0.55.3 1 / 12
0.55.2 1 / 12
0.55.1 1 / 12
0.55.0 1 / 13
0.54.0 1 / 13
0.53.2 1 / 13
0.53.1 1 / 13
0.53.0 1 / 16
0.52.1 1 / 17
0.52.0 1 / 17

v0.54.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.53.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v0.53.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

INFO Publisher changed: pichlermarc → dyladan (on 2025-01-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (dyladan) than the most recent previously approved version (pichlermarc) on 2025-01-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.53.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.52.1

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.

v0.52.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.