← Home

@opentelemetry/propagator-aws-xray

npm Repository Homepage
7
Versions
—
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

opentelemetrynodejstracingprofilingawsxray

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Moved to GitHub Actions CI publishing for the open-telemetry org; SLSA attestation confirms legitimacy. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer roster changes are normal for large org-owned monorepo projects. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects major version bump (v1→v2) in the opentelemetry-js-contrib monorepo. ai

Versions (showing 7 of 7)

Version Deps Published
2.2.0 0 / 2
2.1.4 0 / 2
2.1.3 0 / 20
2.1.2 0 / 20
2.1.1 0 / 20
2.1.0 0 / 21
1.25.1 1 / 20

v2.2.0

1 finding
INFO Has SLSA provenance attestation provenance

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

v2.1.4

2 findings
HIGH Publisher changed: pichlermarc → GitHub Actions (on 2025-11-24) provenance

This version was published by a different npm account than previous versions on 2025-11-24. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

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

v2.1.3

2 findings
HIGH Publisher changed: pichlermarc → GitHub Actions (on 2025-09-29) provenance

This version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

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

v2.1.2

2 findings
HIGH Publisher changed: pichlermarc → GitHub Actions (on 2025-09-29) provenance

This version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

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

v2.1.1

2 findings
HIGH Publisher changed: pichlermarc → dyladan (on 2025-09-01) provenance

This version was published by a different npm account than previous versions on 2025-09-01. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

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

v2.1.0

2 findings
HIGH Publisher changed: pichlermarc → dyladan (on 2025-05-05) provenance

This version was published by a different npm account than previous versions on 2025-05-05. This could indicate a legitimate maintainer transition or an account compromise.

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.

v1.25.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.