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, 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 |
|---|---|---|---|---|
| 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 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 15.25.3 | 24 / 13 | |
| 15.25.2 | 24 / 13 | |
| 15.25.1 | 24 / 13 | |
| 15.25.0 | 24 / 13 | |
| 15.24.3 | 24 / 13 | |
| 15.24.2 | 24 / 13 | |
| 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 | |
| 15.22.4 | 24 / 13 | |
| 15.22.3 | 24 / 13 | |
| 15.22.2 | 24 / 13 | |
| 15.22.1 | 24 / 13 | |
| 15.22.0 | 24 / 13 | |
| 15.21.1 | 23 / 13 | |
| 15.21.0 | 23 / 13 | |
| 15.20.1 | 23 / 14 | |
| 15.20.0 | 23 / 14 | |
| 15.19.0 | 23 / 14 | |
| 15.18.0 | 23 / 14 | |
| 15.17.1 | 23 / 14 | |
| 15.17.0 | 23 / 14 | |
| 15.16.0 | 23 / 14 |
v15.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.