← Home

eiows

high-performance Node.js WebSocket engine for Socket.IO

7
Versions
MIT
License
Yes
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

mmdevries

Keywords

websocketengine.iosocket.ioeiows

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Native C++ addon; 'make' is standard pre-build step for this package. ai
install-scripts install-script:install AI (install-scripts): node-gyp rebuild is the canonical native addon build command. ai
install-scripts install-script:postinstall AI (install-scripts): 'make clean' is standard cleanup after native build; stable for this package. ai

Versions (showing 7 of 7)

Version Deps Published
9.2.0 0 / 0
9.1.0 0 / 0
9.0.3 0 / 0
9.0.2 0 / 0
9.0.1 0 / 0
9.0.0 0 / 0
8.2.1 0 / 0

v9.2.0

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1

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.

v9.1.0

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1

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.

v9.0.3

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1

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.

v9.0.2

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1

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.

v9.0.1

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1

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.

v9.0.0

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1

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.

v8.2.1

4 findings
HIGH Package has 'preinstall' script install-scripts

Script: make

HIGH Package has 'postinstall' script install-scripts

Script: make clean

HIGH Package has 'install' script install-scripts

Script: node-gyp rebuild > build_log.txt 2>&1 || exit 0

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.