@types/ws
TypeScript definitions for 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://github.com/loyd | AI (email-domain): The 'email' field contains a GitHub profile URL, not an actual email address. The analyzer misidentifies the URL as an email domain. No real hijacking risk; github.com is a live domain. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @types/ws is the official DefinitelyTyped scoped package for the 'ws' library, not a typosquat of 'qs'. The @types/ scope makes this comparison meaningless. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @types/ws is the official DefinitelyTyped scoped package for the 'ws' library, not a typosquat of 'pg'. The @types/ scope makes this comparison meaningless. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a standard convention dependency for @types/ packages; it is loaded by TypeScript tooling by convention, not via explicit imports. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 8.18.1 | 1 / 0 | |
| 8.18.0 | 1 / 0 | |
| 8.5.14 | 1 / 0 | |
| 8.5.13 | 1 / 0 | |
| 8.5.12 | 1 / 0 | |
| 8.5.11 | 1 / 0 | |
| 8.5.10 | 1 / 0 | |
| 8.5.9 | 1 / 0 | |
| 8.5.8 | 1 / 0 | |
| 8.5.7 | 1 / 0 | |
| 8.5.6 | 1 / 0 | |
| 8.5.5 | 1 / 0 | |
| 8.5.4 | 1 / 0 | |
| 8.5.3 | 1 / 0 | |
| 8.5.2 | 1 / 0 | |
| 8.5.1 | 1 / 0 | |
| 8.5.0 | 1 / 0 | |
| 8.2.3 | 1 / 0 | |
| 8.2.2 | 1 / 0 | |
| 8.2.1 | 1 / 0 | |
| 8.2.0 | 1 / 0 | |
| 7.4.7 | 1 / 0 | |
| 7.4.6 | 1 / 0 | |
| 7.4.5 | 1 / 0 | |
| 7.4.4 | 1 / 0 | |
| 7.4.3 | 1 / 0 | |
| 7.4.2 | 1 / 0 | |
| 7.4.1 | 1 / 0 | |
| 7.4.0 | 1 / 0 | |
| 7.2.9 | 1 / 0 | |
| 7.2.8 | 1 / 0 | |
| 7.2.7 | 1 / 0 | |
| 7.2.6 | 1 / 0 | |
| 7.2.5 | 1 / 0 | |
| 7.2.4 | 1 / 0 | |
| 7.2.3 | 1 / 0 | |
| 7.2.2 | 1 / 0 | |
| 7.2.1 | 1 / 0 | |
| 7.2.0 | 1 / 0 | |
| 6.0.4 | 1 / 0 | |
| 6.0.3 | 1 / 0 | |
| 6.0.2 | 1 / 0 | |
| 6.0.1 | 2 / 0 | |
| 6.0.0 | 2 / 0 | |
| 5.1.2 | 2 / 0 | |
| 5.1.1 | 2 / 0 | |
| 5.1.0 | 2 / 0 | |
| 4.0.2 | 2 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.2.1 | 1 / 0 | |
| 3.2.0 | 1 / 0 | |
| 3.0.2 | 1 / 0 | |
| 3.0.1 | 1 / 0 | |
| 3.0.0 | 1 / 0 | |
| 0.0.42 | 1 / 0 | |
| 0.0.41 | 1 / 0 | |
| 0.0.40 | 1 / 0 | |
| 0.0.39 | 1 / 0 | |
| 0.0.38 | 1 / 0 | |
| 0.0.37 | 1 / 0 | |
| 0.0.36 | 1 / 0 | |
| 0.0.35 | 1 / 0 | |
| 0.0.34 | 1 / 0 | |
| 0.0.33 | 1 / 0 | |
| 0.0.32 | 1 / 0 | |
| 0.0.31 | 1 / 0 | |
| 0.0.30 | 1 / 0 | |
| 0.0.29 | 1 / 0 | |
| 0.0.27 | 1 / 0 |
v8.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
2 findingsMaintainer email 'https://github.com/loyd' uses domain 'https://github.com/loyd' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.