@volcengine/diagnostics-tls
OpenClaw Volcengine TLS diagnostics plugin
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:zod | AI (phantom-deps): Bundled ESM/CJS plugin; deps consumed in dist bundle, not directly imported in source files. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api | AI (phantom-deps): Bundled plugin; OpenTelemetry deps consumed in dist bundle. | ai | |
| phantom-deps | phantom-dep:@volcengine/openapi | AI (phantom-deps): Same-org dep consumed in bundled dist output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api-logs | AI (phantom-deps): Bundled plugin; OpenTelemetry deps consumed in dist bundle. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Bundled plugin; OpenTelemetry deps consumed in dist bundle. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-base | AI (phantom-deps): Bundled plugin; OpenTelemetry deps consumed in dist bundle. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): Bundled plugin; OpenTelemetry deps consumed in dist bundle. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-proto | AI (phantom-deps): Bundled plugin; OpenTelemetry deps consumed in dist bundle. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.9 | 8 / 5 | |
| 0.0.8 | 8 / 5 | |
| 0.0.7 | 8 / 5 | |
| 0.0.6 | 8 / 5 | |
| 0.0.5 | 8 / 5 | |
| 0.0.4 | 8 / 5 | |
| 0.0.3 | 8 / 5 | |
| 0.0.2 | 8 / 5 | |
| 0.0.1 | 8 / 0 |
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.