@nut-tree-fork/libnut-win32
libnut is an N-API module for desktop automation with node
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled DLLs are standard MSVC runtime redistributables; libnut.node is the expected prebuilt N-API native addon. Normal distribution pattern for Windows native Node addons built with cmake-js. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in patch-packagename.js loads only the local package.json via a deterministic path (join(__dirname, 'package.json')). Not a security risk; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.7.5 | 1 / 2 | |
| 2.7.4 | 1 / 2 | |
| 2.7.3 | 1 / 2 | |
| 2.7.2 | 1 / 2 | |
| 2.7.1 | 1 / 2 |
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.