@zwave-js/cc
zwave-js: Command Classes
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @zwave-js/cc cannot be a typosquat of 'pg'; Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @zwave-js/cc cannot be a typosquat of 'qs'; Levenshtein match is spurious. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known implicit runtime dependency for decorator-based packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:ansi-colors | AI (phantom-deps): Used in config/build tooling context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@zwave-js/host | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for type-only or indirect imports within monorepos. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 15.24.2 | 7 / 13 | |
| 15.24.0 | 7 / 13 | |
| 15.23.5 | 7 / 13 | |
| 15.23.3 | 7 / 13 | |
| 15.23.1 | 7 / 13 | |
| 15.23.0 | 7 / 13 | |
| 15.22.5 | 7 / 13 |
v15.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.