@arcblock/ws
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @arcblock org package; name reflects 'websocket', not a squatter of 'qs'. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same rationale; @arcblock/ws is a legitimate websocket package, not related to 'pg'. | ai |
Versions (showing 51 of 123)
| Version | Deps | Published |
|---|---|---|
| 1.30.24 | 6 / 4 | |
| 1.30.23 | 6 / 4 | |
| 1.30.22 | 6 / 4 | |
| 1.30.21 | 6 / 4 | |
| 1.30.20 | 6 / 4 | |
| 1.30.19 | 6 / 4 | |
| 1.30.18 | 6 / 4 | |
| 1.30.17 | 6 / 4 | |
| 1.30.16 | 6 / 4 | |
| 1.30.15 | 6 / 4 | |
| 1.30.14 | 6 / 4 | |
| 1.30.13 | 6 / 4 | |
| 1.30.12 | 6 / 4 | |
| 1.30.11 | 6 / 4 | |
| 1.30.10 | 6 / 4 | |
| 1.30.9 | 6 / 4 | |
| 1.30.8 | 6 / 4 | |
| 1.30.7 | 6 / 4 | |
| 1.30.6 | 6 / 4 | |
| 1.30.5 | 6 / 4 | |
| 1.30.4 | 6 / 4 | |
| 1.30.3 | 6 / 4 | |
| 1.30.2 | 6 / 4 | |
| 1.30.1 | 6 / 4 | |
| 1.30.0 | 6 / 4 | |
| 1.29.27 | 6 / 4 | |
| 1.29.26 | 6 / 4 | |
| 1.29.25 | 6 / 4 | |
| 1.29.24 | 6 / 4 | |
| 1.29.23 | 6 / 4 | |
| 1.29.22 | 6 / 4 | |
| 1.29.21 | 6 / 4 | |
| 1.29.20 | 6 / 4 | |
| 1.29.19 | 6 / 4 | |
| 1.29.18 | 6 / 4 | |
| 1.29.17 | 6 / 4 | |
| 1.29.16 | 6 / 4 | |
| 1.29.15 | 6 / 4 | |
| 1.29.14 | 6 / 4 | |
| 1.29.13 | 6 / 4 | |
| 1.29.12 | 6 / 4 | |
| 1.29.11 | 6 / 4 | |
| 1.29.10 | 6 / 4 | |
| 1.29.9 | 6 / 4 | |
| 1.29.8 | 6 / 4 | |
| 1.29.7 | 6 / 4 | |
| 1.29.6 | 6 / 4 | |
| 1.29.5 | 6 / 4 | |
| 1.29.4 | 6 / 4 | |
| 1.29.3 | 6 / 4 | |
| 1.29.2 | 6 / 4 |
v1.30.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.11
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.6
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.5
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.27
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.25
2 findingsPackage name '@arcblock/ws' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.