@zwave-js/config
zwave-js: configuration files
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:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit usage is expected. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): eslint is used in config lint scripts; declared as runtime dep intentionally. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston is a logging dep used via config bindings; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ansi-colors | AI (phantom-deps): ansi-colors used in config tooling scripts; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Config-data package in a large monorepo; minimal README and no keywords are expected for internal packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 15.24.2 | 11 / 21 | |
| 15.24.0 | 11 / 21 | |
| 15.23.5 | 11 / 21 | |
| 15.23.3 | 11 / 21 | |
| 15.23.1 | 11 / 21 | |
| 15.23.0 | 11 / 21 | |
| 15.22.5 | 11 / 21 |
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.