@zwave-js/serial
zwave-js: Serialport driver
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): zwave-js monorepo migrated publishing to GitHub Actions CI; consistent with org-level automation change. | ai | |
| phantom-deps | phantom-dep:@zwave-js/host | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Referenced in config files; stable false positive for this logging-aware package. | ai | |
| phantom-deps | phantom-dep:@serialport/stream | AI (phantom-deps): Referenced in config files; stable false positive for this serialport driver package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 15.26.0 | 9 / 12 | |
| 15.25.3 | 9 / 12 | |
| 15.25.2 | 9 / 12 | |
| 15.25.1 | 9 / 12 | |
| 15.25.0 | 9 / 12 | |
| 15.24.3 | 9 / 12 | |
| 15.24.2 | 9 / 12 | |
| 15.24.0 | 9 / 12 | |
| 15.23.5 | 9 / 12 | |
| 15.23.3 | 9 / 12 | |
| 15.23.1 | 9 / 12 | |
| 15.23.0 | 9 / 12 | |
| 15.22.5 | 9 / 12 | |
| 15.22.4 | 9 / 12 | |
| 15.22.1 | 9 / 12 | |
| 15.22.0 | 9 / 12 | |
| 15.21.1 | 8 / 12 | |
| 15.21.0 | 8 / 12 | |
| 15.20.1 | 8 / 12 | |
| 15.20.0 | 8 / 12 | |
| 15.19.0 | 8 / 12 | |
| 15.18.0 | 8 / 12 | |
| 15.17.0 | 8 / 12 | |
| 15.16.0 | 8 / 12 | |
| 15.15.3 | 8 / 12 | |
| 15.15.2 | 8 / 12 | |
| 15.15.1 | 8 / 12 | |
| 15.15.0 | 8 / 12 | |
| 15.14.0 | 8 / 12 | |
| 15.13.0 | 8 / 12 | |
| 15.12.0 | 8 / 12 | |
| 15.11.0 | 8 / 12 | |
| 15.10.0 | 8 / 12 | |
| 15.9.0 | 8 / 12 | |
| 15.8.0 | 8 / 12 | |
| 15.7.0 | 8 / 12 | |
| 15.6.0 | 8 / 12 | |
| 15.5.0 | 8 / 12 | |
| 15.4.0 | 8 / 12 | |
| 15.3.2 | 8 / 12 | |
| 15.3.1 | 8 / 12 | |
| 15.3.0 | 8 / 12 | |
| 15.2.1 | 8 / 12 | |
| 15.2.0 | 8 / 12 | |
| 15.1.2 | 8 / 12 | |
| 15.1.1 | 8 / 12 | |
| 15.1.0 | 8 / 12 | |
| 15.0.6 | 8 / 12 | |
| 15.0.4 | 8 / 12 | |
| 15.0.2 | 8 / 12 | |
| 15.0.1 | 8 / 12 |
v15.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.