← Home

@sorrell/wm-windows

The primary API through which SorrellWm interacts with the Windows API.

8
Versions
MIT
License
No
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

sorrell

Keywords

sorrellwmc++cppnative-modulewindowswin32windows-apicmake

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Native addon package; CMake build artifacts and .node binary are expected outputs for a cmake-js C++ addon. ai
phantom-deps phantom-dep:bindings AI (phantom-deps): bindings is a native addon runtime dep referenced in build config, not directly imported in JS — stable false positive for this package. ai
phantom-deps phantom-dep:node-addon-api AI (phantom-deps): node-addon-api is a C++ header-only build dep for native addons; not imported in JS — stable false positive. ai
phantom-deps phantom-dep:node-api-headers AI (phantom-deps): node-api-headers is a build-time C header dep; not imported in JS — stable false positive. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.7 3 / 1
1.0.6 3 / 1
1.0.5 3 / 1
1.0.4 3 / 1
1.0.3 3 / 1
1.0.2 3 / 1
1.0.1 3 / 1
1.0.0 3 / 1

v1.0.7

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.6

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.5

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.4

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.3

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.2

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.1

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_C.bin • Build/CMakeFiles/4.2.1/CMakeDetermineCompilerABI_CXX.bin • Build/CMakeFiles/4.2.1/CompilerIdC/CompilerIdC.exe • Build/CMakeFiles/4.2.1/CompilerIdCXX/CompilerIdCXX.exe • Build/Release/SorrellWmWindows.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.

v1.0.0

1 finding
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.