ky
Tiny and elegant HTTP client based on the Fetch API
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): ky is a TypeScript ESM package that compiles to a distribution/ directory; restructuring output into multiple files is expected across versions for this package. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus/ky is a well-established package from a highly trusted publisher; lack of Sigstore provenance is not a meaningful risk signal for this package. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): ky is a legitimate, well-known HTTP client by sindresorhus. Short 2-char name triggers Levenshtein false positives; not a typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): ky is a legitimate, well-known HTTP client by sindresorhus. Short 2-char name triggers Levenshtein false positives; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): ky is a legitimate, well-known HTTP client by sindresorhus. Short 2-char name triggers Levenshtein false positives; not a typosquat of qs. | ai |
Versions (showing 97 of 97)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 0 / 15 | |
| 2.0.1 | 0 / 15 | |
| 2.0.0 | 0 / 15 | |
| 1.14.3 | 0 / 20 | |
| 1.14.2 | 0 / 20 | |
| 1.14.1 | 0 / 20 | |
| 1.14.0 | 0 / 20 | |
| 1.13.0 | 0 / 20 | |
| 1.12.0 | 0 / 20 | |
| 1.11.0 | 0 / 20 | |
| 1.10.0 | 0 / 20 | |
| 1.9.1 | 0 / 20 | |
| 1.9.0 | 0 / 20 | |
| 1.8.2 | 0 / 20 | |
| 1.8.1 | 0 / 20 | |
| 1.8.0 | 0 / 20 | |
| 1.7.5 | 0 / 19 | |
| 1.7.4 | 0 / 19 | |
| 1.7.3 | 0 / 19 | |
| 1.7.2 | 0 / 19 | |
| 1.7.1 | 0 / 19 | |
| 1.7.0 | 0 / 19 | |
| 1.6.0 | 0 / 19 | |
| 1.5.0 | 0 / 19 | |
| 1.4.0 | 0 / 19 | |
| 1.3.0 | 0 / 19 | |
| 1.2.4 | 0 / 19 | |
| 1.2.3 | 0 / 19 | |
| 1.2.2 | 0 / 19 | |
| 1.2.1 | 0 / 19 | |
| 1.2.0 | 0 / 19 | |
| 1.1.3 | 0 / 19 | |
| 1.1.2 | 0 / 19 | |
| 1.1.1 | 0 / 19 | |
| 1.1.0 | 0 / 19 | |
| 1.0.1 | 0 / 19 | |
| 1.0.0 | 0 / 19 | |
| 0.33.3 | 0 / 23 | |
| 0.33.2 | 0 / 23 | |
| 0.33.1 | 0 / 23 | |
| 0.33.0 | 0 / 23 | |
| 0.32.2 | 0 / 23 | |
| 0.32.1 | 0 / 23 | |
| 0.32.0 | 0 / 23 | |
| 0.31.4 | 0 / 22 | |
| 0.31.3 | 0 / 22 | |
| 0.31.2 | 0 / 22 | |
| 0.31.1 | 0 / 23 | |
| 0.31.0 | 0 / 23 | |
| 0.30.0 | 0 / 22 | |
| 0.29.0 | 0 / 22 | |
| 0.28.7 | 0 / 22 | |
| 0.28.6 | 0 / 22 | |
| 0.28.5 | 0 / 21 | |
| 0.28.4 | 0 / 21 | |
| 0.28.3 | 0 / 21 | |
| 0.28.2 | 0 / 21 | |
| 0.28.1 | 0 / 21 | |
| 0.28.0 | 0 / 21 | |
| 0.27.0 | 0 / 12 | |
| 0.26.0 | 0 / 12 | |
| 0.25.1 | 0 / 14 | |
| 0.25.0 | 0 / 15 | |
| 0.24.0 | 0 / 15 | |
| 0.23.0 | 0 / 15 | |
| 0.22.0 | 0 / 15 | |
| 0.21.0 | 0 / 15 | |
| 0.20.0 | 0 / 15 | |
| 0.19.1 | 0 / 15 | |
| 0.19.0 | 0 / 15 | |
| 0.18.0 | 0 / 15 | |
| 0.17.0 | 0 / 14 | |
| 0.16.2 | 0 / 14 | |
| 0.16.1 | 0 / 13 | |
| 0.16.0 | 0 / 13 | |
| 0.15.0 | 0 / 13 | |
| 0.14.0 | 0 / 13 | |
| 0.13.0 | 0 / 13 | |
| 0.12.0 | 0 / 13 | |
| 0.11.2 | 0 / 13 | |
| 0.11.1 | 0 / 13 | |
| 0.11.0 | 0 / 13 | |
| 0.10.0 | 0 / 13 | |
| 0.9.1 | 0 / 13 | |
| 0.9.0 | 0 / 14 | |
| 0.8.0 | 0 / 14 | |
| 0.7.1 | 0 / 13 | |
| 0.7.0 | 0 / 13 | |
| 0.6.0 | 0 / 12 | |
| 0.5.2 | 0 / 12 | |
| 0.5.1 | 0 / 12 | |
| 0.5.0 | 0 / 12 | |
| 0.4.1 | 0 / 10 | |
| 0.4.0 | 0 / 10 | |
| 0.3.0 | 0 / 10 | |
| 0.2.0 | 0 / 7 | |
| 0.1.0 | 2 / 1 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.