@zuplo/otel
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ts-checked-fsm | AI (phantom-deps): ts-checked-fsm is a declared dependency used in build config; phantom-dep false positive for this bundled package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal utility package in a large corporate monorepo; missing README/keywords/description is consistent with the package's nature across all 1493 versions. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api-logs | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/api-logs is declared in dependencies. Not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/resources is declared in dependencies. Not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/otlp-transformer | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/otlp-transformer is declared in dependencies. Not a true phantom dep. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fired on standard bundler output (esbuild/rollup minification). The sample shows Object.defineProperty for function naming, not malicious Reflect.get() usage. False positive for this bundled package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/semantic-conventions is declared in dependencies. Not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/exporter-trace-otlp-http is declared in dependencies. Not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/otlp-exporter-base | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/otlp-exporter-base is declared in dependencies. Not a true phantom dep. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): Package bundles its deps into ESM output; @opentelemetry/core is declared in dependencies. Not a true phantom dep. | ai |
Versions (showing 100 of 1090)
| Version | Deps | Published |
|---|---|---|
| 6.45.1 | 9 / 2 | |
| 6.45.0 | 9 / 2 | |
| 6.44.18 | 9 / 2 | |
| 6.44.17 | 9 / 2 | |
| 6.44.15 | 9 / 2 | |
| 6.44.14 | 9 / 2 | |
| 6.44.13 | 9 / 2 | |
| 6.44.12 | 9 / 2 | |
| 6.44.11 | 9 / 2 | |
| 6.44.10 | 9 / 2 | |
| 6.44.9 | 9 / 2 | |
| 6.44.8 | 9 / 2 | |
| 6.44.7 | 9 / 2 | |
| 6.44.6 | 9 / 2 | |
| 6.44.5 | 9 / 2 | |
| 6.44.4 | 9 / 2 | |
| 6.44.3 | 9 / 2 | |
| 6.44.2 | 9 / 2 | |
| 6.44.1 | 9 / 2 | |
| 6.44.0 | 9 / 2 | |
| 6.43.21 | 9 / 2 | |
| 6.43.20 | 9 / 2 | |
| 6.43.19 | 9 / 2 | |
| 6.43.18 | 9 / 2 | |
| 6.43.17 | 9 / 2 | |
| 6.43.16 | 9 / 2 | |
| 6.43.15 | 9 / 2 | |
| 6.43.14 | 9 / 2 | |
| 6.43.13 | 9 / 2 | |
| 6.43.12 | 9 / 2 | |
| 6.43.11 | 9 / 2 | |
| 6.43.10 | 9 / 2 | |
| 6.43.9 | 9 / 2 | |
| 6.43.8 | 9 / 2 | |
| 6.43.7 | 9 / 2 | |
| 6.43.6 | 9 / 2 | |
| 6.43.5 | 9 / 2 | |
| 6.43.4 | 9 / 2 | |
| 6.43.3 | 9 / 2 | |
| 6.43.2 | 9 / 2 | |
| 6.43.1 | 9 / 2 | |
| 6.43.0 | 9 / 2 | |
| 6.42.1 | 9 / 2 | |
| 6.42.0 | 9 / 2 | |
| 6.41.7 | 9 / 2 | |
| 6.41.6 | 9 / 2 | |
| 6.41.5 | 9 / 2 | |
| 6.41.4 | 9 / 2 | |
| 6.41.3 | 9 / 2 | |
| 6.41.2 | 9 / 2 | |
| 6.41.1 | 9 / 2 | |
| 6.40.40 | 9 / 2 | |
| 6.40.39 | 9 / 2 | |
| 6.40.38 | 9 / 2 | |
| 6.40.37 | 9 / 2 | |
| 6.40.36 | 9 / 2 | |
| 6.40.35 | 9 / 2 | |
| 6.40.34 | 9 / 2 | |
| 6.40.33 | 9 / 2 | |
| 6.40.32 | 9 / 2 | |
| 6.40.31 | 9 / 2 | |
| 6.40.30 | 9 / 2 | |
| 6.40.29 | 9 / 2 | |
| 6.40.28 | 9 / 2 | |
| 6.40.27 | 9 / 2 | |
| 6.40.26 | 9 / 2 | |
| 6.40.25 | 9 / 2 | |
| 6.40.24 | 9 / 2 | |
| 6.40.23 | 9 / 2 | |
| 6.40.22 | 9 / 2 | |
| 6.40.21 | 9 / 2 | |
| 6.40.20 | 9 / 2 | |
| 6.40.19 | 9 / 2 | |
| 6.40.18 | 9 / 2 | |
| 6.40.17 | 9 / 2 | |
| 6.40.16 | 9 / 2 | |
| 6.40.15 | 9 / 2 | |
| 6.40.12 | 9 / 2 | |
| 6.40.11 | 9 / 2 | |
| 6.40.10 | 9 / 2 | |
| 6.40.9 | 9 / 2 | |
| 6.40.8 | 9 / 2 | |
| 6.40.7 | 9 / 2 | |
| 6.40.6 | 9 / 2 | |
| 6.40.5 | 9 / 2 | |
| 6.40.4 | 9 / 2 | |
| 6.40.3 | 9 / 2 | |
| 6.40.2 | 9 / 2 | |
| 6.40.1 | 9 / 2 | |
| 6.40.0 | 9 / 2 | |
| 6.39.47 | 9 / 2 | |
| 6.39.46 | 9 / 2 | |
| 6.39.45 | 9 / 2 | |
| 6.39.44 | 9 / 2 | |
| 6.39.43 | 9 / 2 | |
| 6.39.42 | 9 / 2 | |
| 6.39.41 | 9 / 2 | |
| 6.39.40 | 9 / 2 | |
| 6.39.39 | 9 / 2 | |
| 6.39.38 | 9 / 2 |
v6.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.39.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.