sockjs-client — Greenflagged

SockJS-client is a browser JavaScript library that provides a WebSocket-like object.

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

brycekahle

Keywords

websocketswebsocket

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:lib/shims.js	AI (source-diff): lib/shims.js is an ES5 polyfill from es-shims/es5-shim; no actual network or malicious code execution.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): brycekahle is the documented new maintainer of sockjs-client under the official sockjs GitHub org.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): msackman removal is part of the documented maintainer transition for sockjs-client 1.0.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change to brycekahle is a legitimate, documented maintainer transition for sockjs-client.	ai	2026/04/24
maintainer-change	maintainer-takeover	AI (maintainer-change): Bryce Kahle is a listed contributor and long-time maintainer of sockjs-client; legitimate transition for 1.0 rewrite.	ai	2026/04/24
source-diff	net-exec-file:dist/sockjs.min.js	AI (source-diff): Minified version of the same Browserify browser bundle; same rationale as the unminified dist file.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from adding dist/ browser bundles and source maps; expected when a package starts shipping pre-built assets.	ai	2026/04/24
source-diff	net-exec-file:dist/sockjs.js	AI (source-diff): Standard Browserify browser bundle for sockjs-client; network+exec pattern is the library's core WebSocket/XHR transport functionality.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
1.6.1	5 / 22	2022-05-28
1.6.0	5 / 22	2022-02-27
1.5.2	6 / 22	2021-08-24
1.5.1	6 / 22	2021-03-25
1.5.0	6 / 22	2020-08-02
1.4.0	6 / 22	2019-08-22
1.3.0	6 / 22	2018-09-24
1.2.0	6 / 22	2018-09-21
1.1.5	6 / 19	2018-05-29
1.1.4	6 / 19	2017-04-30
1.1.2	6 / 19	2017-01-23
1.1.1	6 / 17	2016-05-20
1.1.0	6 / 17	2016-04-30
1.0.3	6 / 17	2015-07-31
1.0.2	6 / 17	2015-07-22
1.0.1	6 / 17	2015-07-20
1.0.0	6 / 17	2015-05-14
0.1.3	1 / 0	2012-05-01
0.1.2	1 / 0	2012-04-02
0.1.1	1 / 0	2012-03-23
0.1.0	1 / 0	2012-03-23

v1.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

3 findings

HIGH New file with network + code execution: dist/sockjs.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/sockjs.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

3 findings

HIGH New file with network + code execution: dist/sockjs.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/sockjs.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

4 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (msackman) were replaced by new maintainers (brycekahle). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: msackman → brycekahle (on 2015-05-14) provenance

This version was published by a different npm account than previous versions on 2015-05-14. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: lib/shims.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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