@opentelemetry/sdk-trace-node Apache-2.0 59 versions

@opentelemetry/sdk-trace-node

npm Repository Homepage

OpenTelemetry Node SDK provides automatic telemetry (tracing, metrics, etc) for Node.js applications

59

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

dyladanpichlermarcoverbalancenpmjs-accounttrentmmartinkuba

Keywords

opentelemetrynodejstracingprofilingmetricsstats

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): OpenTelemetry JS migrated to GitHub Actions CI/CD publishing with SLSA provenance attestation. Publisher change from named maintainer to GitHub Actions is a legitimate and documented supply chain improvement for this org.	ai	2026/04/23

Versions (showing 59 of 59)

Version	Deps	Published
2.9.0	3 / 10	2026-07-02
2.8.0	3 / 10	2026-06-11
2.7.1	3 / 10	2026-04-29
2.7.0	3 / 10	2026-04-17
2.6.1	3 / 10	2026-03-25
2.6.0	3 / 10	2026-03-03
2.5.1	3 / 10	2026-02-12
2.5.0	3 / 10	2026-01-21
2.4.0	3 / 10	2026-01-14
2.3.0	3 / 10	2026-01-08
2.2.0	3 / 10	2025-10-21
2.1.0	3 / 11	2025-09-04
2.0.1	3 / 12	2025-05-15
2.0.0	3 / 12	2025-03-17
1.30.1	6 / 13	2025-01-14
1.30.0	6 / 13	2024-12-18
1.29.0	6 / 13	2024-12-04
1.28.0	6 / 13	2024-11-18
1.27.0	6 / 13	2024-10-23
1.26.0	6 / 14	2024-08-28
1.25.1	6 / 15	2024-06-20
1.25.0	6 / 15	2024-06-05
1.24.1	6 / 15	2024-05-07
1.24.0	6 / 15	2024-04-24
1.23.0	6 / 15	2024-04-03
1.22.0	6 / 15	2024-02-29
1.21.0	6 / 15	2024-01-26
1.20.0	6 / 15	2024-01-15
1.19.0	6 / 15	2023-12-14
1.18.1	6 / 15	2023-11-08
1.18.0	6 / 15	2023-11-07
1.17.1	6 / 15	2023-10-10
1.17.0	6 / 15	2023-09-12
1.16.0	6 / 15	2023-09-11
1.15.2	6 / 15	2023-08-08
1.15.1	6 / 15	2023-07-24
1.15.0	7 / 15	2023-07-06
1.14.0	6 / 13	2023-06-06
1.13.0	6 / 13	2023-05-11
1.12.0	6 / 14	2023-04-13
1.11.0	6 / 14	2023-03-30
1.10.1	6 / 14	2023-03-20
1.10.0	6 / 14	2023-03-13
1.9.1	6 / 14	2023-01-30
1.9.0	6 / 14	2023-01-11
1.8.0	6 / 14	2022-11-09
1.7.0	6 / 14	2022-09-16
1.6.0	6 / 14	2022-08-24
1.5.0	6 / 14	2022-07-26
1.4.0	6 / 14	2022-07-06
1.3.1	6 / 14	2022-06-06
1.3.0	6 / 14	2022-05-27
1.2.0	6 / 14	2022-04-22
1.1.1	6 / 14	2022-03-22
1.1.0	6 / 14	2022-03-18
1.0.1	6 / 14	2021-11-11
1.0.0	6 / 14	2021-09-30
0.26.0	6 / 14	2021-09-30
0.25.0	6 / 16	2021-08-18

v2.9.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.8.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.

v1.23.0

1 finding

LOW No provenance attestation provenance

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

v1.22.0

1 finding

LOW No provenance attestation provenance

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

v1.21.0

1 finding

LOW No provenance attestation provenance

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

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.19.0

1 finding

LOW No provenance attestation provenance

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

v1.18.1

1 finding

LOW No provenance attestation provenance

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

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.1

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dyladan → pichlermarc (on 2023-08-08) provenance

[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.

v1.15.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: pichlermarc → dyladan (on 2023-07-24) provenance

[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.

v1.15.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dyladan → pichlermarc (on 2023-07-06) provenance

[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.

v1.14.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dyladan → pichlermarc (on 2023-06-06) provenance

[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.

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

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