@zwave-js/nvmedit
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 to GitHub Actions publishing; consistent with CI/CD automation for this established package. | ai | |
| provenance | no-provenance | AI (provenance): Established zwave-js monorepo; provenance absence is consistent across all versions and not a risk signal here. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 15.25.3 | 7 / 9 | |
| 15.25.2 | 7 / 9 | |
| 15.25.0 | 7 / 9 | |
| 15.24.3 | 7 / 9 | |
| 15.24.2 | 7 / 9 | |
| 15.24.0 | 7 / 9 | |
| 15.23.1 | 7 / 9 | |
| 15.23.0 | 7 / 9 | |
| 15.22.1 | 7 / 9 | |
| 15.22.0 | 7 / 9 | |
| 15.21.0 | 6 / 9 | |
| 15.20.0 | 6 / 9 | |
| 15.19.0 | 6 / 9 | |
| 15.18.0 | 6 / 9 | |
| 15.17.0 | 6 / 9 | |
| 15.16.0 | 6 / 9 | |
| 15.15.3 | 6 / 9 | |
| 15.15.2 | 6 / 9 | |
| 15.15.1 | 6 / 9 | |
| 15.15.0 | 6 / 9 | |
| 15.14.0 | 6 / 9 | |
| 15.13.0 | 6 / 9 | |
| 15.11.0 | 6 / 9 | |
| 15.10.0 | 6 / 9 | |
| 15.9.0 | 6 / 9 | |
| 15.7.0 | 6 / 9 | |
| 15.6.0 | 6 / 9 | |
| 15.4.0 | 6 / 9 | |
| 15.3.0 | 6 / 9 | |
| 15.2.1 | 6 / 9 | |
| 15.1.2 | 6 / 9 | |
| 15.1.1 | 6 / 9 | |
| 15.1.0 | 6 / 9 | |
| 15.0.6 | 6 / 9 | |
| 15.0.4 | 6 / 9 | |
| 15.0.0 | 6 / 9 |
v15.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.