zwave-js
Z-Wave driver written entirely in JavaScript/TypeScript
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): User-config loader in mock-server CLI; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:serialport | AI (phantom-deps): serialport is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:ansi-colors | AI (phantom-deps): ansi-colors is a declared runtime dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@zwave-js/host | AI (phantom-deps): @zwave-js/host is a declared runtime dep; phantom-dep heuristic false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 15.24.0 | 24 / 13 | |
| 15.23.5 | 24 / 13 | |
| 15.23.4 | 24 / 13 | |
| 15.23.3 | 24 / 13 | |
| 15.23.2 | 24 / 13 | |
| 15.23.1 | 24 / 13 | |
| 15.23.0 | 24 / 13 | |
| 15.22.5 | 24 / 13 |
v15.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.