jaeger-client
Jaeger binding for OpenTracing API for Node.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): js-yaml is declared as a dependency and used in config file handling; not being directly imported in main code is a stable, benign pattern for this package. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): The `request` package is a well-known HTTP client expected in a tracing client like jaeger-client; this is a stable, benign dependency for this package. | ai | |
| provenance | publisher-changed | AI (provenance): wjang (Won Jun Jang) is a listed contributor and Uber/Jaeger team member; legitimate maintainer transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): uuid is a top-tier npm package; expected dependency for a tracing library generating trace/span IDs. | ai | |
| provenance | no-provenance | AI (provenance): Established Uber package predating Sigstore provenance; 804k weekly downloads and long track record make this a stable false positive. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.19.0 | 5 / 35 | |
| 3.18.1 | 5 / 34 | |
| 3.18.0 | 5 / 34 | |
| 3.17.2 | 5 / 34 | |
| 3.17.1 | 5 / 34 | |
| 3.17.0 | 5 / 34 | |
| 3.16.0 | 5 / 34 | |
| 3.15.0 | 5 / 34 | |
| 3.14.4 | 5 / 34 | |
| 3.14.3 | 5 / 34 | |
| 3.14.2 | 5 / 34 | |
| 3.14.1 | 5 / 34 | |
| 3.14.0 | 5 / 34 | |
| 3.13.0 | 5 / 34 | |
| 3.12.0 | 5 / 34 | |
| 3.11.0 | 5 / 34 | |
| 3.10.0 | 4 / 35 | |
| 3.9.1 | 4 / 34 | |
| 3.9.0 | 5 / 34 | |
| 3.8.0 | 4 / 29 | |
| 3.7.0 | 4 / 30 | |
| 3.6.0 | 4 / 30 | |
| 3.5.3 | 4 / 29 | |
| 3.5.2 | 4 / 29 | |
| 3.5.1 | 4 / 29 | |
| 3.5.0 | 4 / 29 | |
| 3.4.0 | 5 / 28 | |
| 3.3.1 | 5 / 28 | |
| 3.2.1 | 5 / 28 | |
| 3.2.0 | 5 / 29 | |
| 3.0.0 | 9 / 28 |
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-09. This could indicate a legitimate maintainer transition or an account compromise.
v3.15.0
2 findingsThis version was published by a different npm account than previous versions on 2019-05-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v3.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
2 findingsThis version was published by a different npm account than previous versions on 2019-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
2 findingsThis version was published by a different npm account than previous versions on 2019-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
2 findingsThis version was published by a different npm account than previous versions on 2019-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-09. This could indicate a legitimate maintainer transition or an account compromise.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
2 findingsThis version was published by a different npm account than previous versions on 2018-07-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.