@traceloop/node-server-sdk No license 37 versions

@traceloop/node-server-sdk

npm Repository Homepage

37

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

tomer-friedmannirgagalklm

Keywords

opentelemetrynodejstracing

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package.	ai	2026/05/21
phantom-deps	phantom-dep:uuid	AI (phantom-deps): uuid is declared and used indirectly via bundled output; stable false positive.	ai	2026/05/21
phantom-deps	phantom-dep:eventsource	AI (phantom-deps): eventsource referenced in config files; stable false positive for this SDK.	ai	2026/05/21
phantom-deps	phantom-dep:supports-color	AI (phantom-deps): supports-color referenced in config; stable false positive for this SDK.	ai	2026/05/21
phantom-deps	phantom-dep:@opentelemetry/instrumentation	AI (phantom-deps): OTel instrumentation is a peer dep used via config; stable false positive.	ai	2026/05/21
phantom-deps	phantom-dep:@types/nunjucks	AI (phantom-deps): Type-only package; stable false positive for this SDK.	ai	2026/05/21

Versions (showing 37 of 37)

Version	Deps	Published
0.27.0	35 / 32	2026-06-01
0.26.0	35 / 32	2026-04-16
0.25.0	34 / 31	2026-04-13
0.24.1	33 / 31	2026-04-12
0.24.0	33 / 31	2026-04-06
0.23.0	33 / 31	2026-03-30
0.22.8	33 / 31	2026-03-04
0.22.7	33 / 31	2026-02-08
0.22.6	33 / 31	2026-01-18
0.22.5	33 / 31	2025-12-17
0.22.4	33 / 31	2025-12-11
0.22.3	33 / 31	2025-12-08
0.22.2	33 / 31	2025-12-02
0.22.1	33 / 30	2025-12-01
0.22.0	33 / 30	2025-11-27
0.21.1	32 / 29	2025-11-25
0.21.0	33 / 29	2025-11-24
0.20.2	32 / 28	2025-11-24
0.19.1	31 / 27	2025-09-21
0.19.0	31 / 27	2025-09-17
0.18.1	31 / 27	2025-08-24
0.18.0	31 / 25	2025-08-24
0.17.1	29 / 25	2025-08-21
0.17.0	29 / 25	2025-08-18
0.16.2	29 / 25	2025-08-17
0.16.1	29 / 25	2025-08-15
0.16.0	29 / 25	2025-08-14
0.15.0	28 / 24	2025-08-11
0.14.6	28 / 24	2025-07-28
0.14.5	28 / 24	2025-07-26
0.14.4	21 / 22	2025-07-21
0.14.3	22 / 22	2025-07-17
0.14.2	22 / 22	2025-07-17
0.14.1	22 / 22	2025-07-07
0.14.0	22 / 22	2025-07-04
0.13.5	22 / 22	2025-06-27
0.13.4	22 / 22	2025-06-10

v0.27.0

2 findings

HIGH Publisher changed: galklm → GitHub Actions (on 2026-06-01) provenance

This version was published by a different npm account than previous versions on 2026-06-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.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.1

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.8

1 finding

LOW No provenance attestation provenance

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

v0.22.7

1 finding

LOW No provenance attestation provenance

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

v0.22.6

1 finding

LOW No provenance attestation provenance

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

v0.22.5

1 finding

LOW No provenance attestation provenance

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

v0.22.4

1 finding

LOW No provenance attestation provenance

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

v0.22.3

1 finding

LOW No provenance attestation provenance

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

v0.22.2

1 finding

LOW No provenance attestation provenance

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

v0.22.1

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.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.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.2

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

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.1

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.2

1 finding

LOW No provenance attestation provenance

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

v0.16.1

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.6

1 finding

LOW No provenance attestation provenance

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

v0.14.5

1 finding

LOW No provenance attestation provenance

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

v0.14.4

1 finding

LOW No provenance attestation provenance

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

v0.14.3

1 finding

LOW No provenance attestation provenance

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

v0.14.2

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.5

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

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.