@zwave-js/server
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): False positive; @zwave-js/server is an established Z-Wave server package, not a typosquat of semver. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): CJS build artifact from ESM-to-CJS conversion tool; not arbitrary module loading. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for Z-Wave network key parsing; legitimate domain use. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding used for Z-Wave NVM backup/restore operations; legitimate domain use. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.8.0 | 3 / 18 | |
| 3.7.0 | 3 / 18 | |
| 3.6.0 | 3 / 18 | |
| 3.5.0 | 3 / 18 | |
| 3.4.0 | 3 / 22 | |
| 3.3.0 | 3 / 22 | |
| 3.2.1 | 3 / 22 | |
| 3.2.0 | 3 / 22 | |
| 3.1.0 | 3 / 22 |
v3.8.0
2 findingsPackage name '@zwave-js/server' is 1 edit(s) away from popular package 'semver'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
2 findingsPackage name '@zwave-js/server' is 1 edit(s) away from popular package 'semver'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.0
2 findingsPackage name '@zwave-js/server' is 1 edit(s) away from popular package 'semver'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
2 findingsPackage name '@zwave-js/server' is 1 edit(s) away from popular package 'semver'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.