@nut-tree-fork/libnut-win32 Apache-2.0 1 versions

@nut-tree-fork/libnut-win32

npm Homepage

libnut is an N-API module for desktop automation with node

Versions

Apache-2.0

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zachjw34

Keywords

GUIAutomationmousekeyboardscreenshotimagedesktopscreenrecognitionautohotkey

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	2026/04/26
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	2026/04/26

Versions (showing 1 of 1)

Version	Deps	Published
2.7.5	1 / 2	2025-03-13

v2.7.5

2 findings

HIGH Bundled binary files (7) npm-metadata

Package contains compiled binaries that could be backdoors: • build/Release/api-ms-win-crt-heap-l1-1-0.dll • build/Release/api-ms-win-crt-runtime-l1-1-0.dll • build/Release/api-ms-win-crt-string-l1-1-0.dll • build/Release/msvcp140.dll • build/Release/vcruntime140_1.dll • build/Release/vcruntime140.dll • build/Release/libnut.node

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.