@finos/legend-extension-tracer-zipkin
Legend extension for tracer using Zipkin and OpenTracing
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): FINOS org publisher with strong track record; no script/dep changes; consistent with infrequent but legitimate release cadence. | ai | |
| dependencies | unvetted-dep:zipkin-javascript-opentracing | AI (dependencies): Core runtime dep for this Zipkin tracing extension; expected and stable across versions. | ai | |
| dependencies | unvetted-dep:@types/zipkin-javascript-opentracing | AI (dependencies): Type definitions for the core dep; benign and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): FINOS org package; provenance absence is consistent across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@types/zipkin-javascript-opentracing | AI (phantom-deps): @types packages are type-only and loaded by convention; not directly imported at runtime. | ai |
Versions (showing 44 of 144)
| Version | Deps | Published |
|---|---|---|
| 3.0.43 | 6 / 8 | |
| 3.0.42 | 6 / 8 | |
| 3.0.41 | 6 / 8 | |
| 3.0.40 | 6 / 8 | |
| 3.0.39 | 6 / 8 | |
| 3.0.38 | 6 / 8 | |
| 3.0.37 | 6 / 8 | |
| 3.0.36 | 6 / 8 | |
| 3.0.35 | 6 / 8 | |
| 3.0.34 | 6 / 8 | |
| 3.0.33 | 6 / 8 | |
| 3.0.32 | 6 / 8 | |
| 3.0.31 | 6 / 8 | |
| 3.0.30 | 6 / 8 | |
| 3.0.29 | 6 / 8 | |
| 3.0.28 | 6 / 8 | |
| 3.0.27 | 6 / 8 | |
| 3.0.26 | 6 / 8 | |
| 3.0.25 | 6 / 8 | |
| 3.0.24 | 6 / 8 | |
| 3.0.23 | 6 / 8 | |
| 3.0.22 | 6 / 8 | |
| 3.0.21 | 6 / 8 | |
| 3.0.20 | 6 / 8 | |
| 3.0.19 | 6 / 8 | |
| 3.0.18 | 6 / 8 | |
| 3.0.17 | 6 / 8 | |
| 3.0.16 | 6 / 8 | |
| 3.0.15 | 6 / 8 | |
| 3.0.14 | 6 / 8 | |
| 3.0.13 | 6 / 8 | |
| 3.0.12 | 6 / 8 | |
| 3.0.11 | 6 / 8 | |
| 3.0.10 | 6 / 8 | |
| 3.0.9 | 6 / 8 | |
| 3.0.8 | 6 / 8 | |
| 3.0.7 | 6 / 8 | |
| 3.0.6 | 6 / 8 | |
| 3.0.5 | 6 / 8 | |
| 3.0.4 | 6 / 8 | |
| 3.0.3 | 6 / 8 | |
| 3.0.2 | 6 / 8 | |
| 3.0.1 | 6 / 8 | |
| 3.0.0 | 6 / 8 |
v3.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.