got
Human-friendly and powerful HTTP request library for Node.js
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): szmarczak is a documented long-standing co-maintainer of got and author of @szmarczak/http-timer (already a dep). The transition from sindresorhus is a known legitimate handoff, not a compromise. | ai | |
| phantom-deps | phantom-dep:@types/cacheable-request | AI (phantom-deps): Type-only dependency; not directly imported at runtime but required for TypeScript consumers. Expected pattern for a TypeScript library. | ai | |
| dependencies | unvetted-dep:@types/responselike | AI (dependencies): got is a TypeScript library that ships types; @types/responselike is a legitimate type-only runtime dep needed by consumers for TypeScript compatibility. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@types/cacheable-request | AI (dependencies): got is a TypeScript library that ships types; @types/cacheable-request is a legitimate type-only runtime dep needed by consumers for TypeScript compatibility. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/responselike | AI (phantom-deps): Type-only dependency; not directly imported at runtime but required for TypeScript consumers. Expected pattern for a TypeScript library. | ai | |
| dependencies | unvetted-dep:@sindresorhus/is | AI (dependencies): @sindresorhus/is is published by the same author (sindresorhus) and is a core utility used across many of his packages. No security concern. | ai | |
| dependencies | unvetted-dep:cacheable-lookup | AI (dependencies): cacheable-lookup is a well-known DNS caching utility, a stable dependency of got. No security concern. | ai | |
| dependencies | unvetted-dep:form-data-encoder | AI (dependencies): form-data-encoder is a legitimate form data encoding package, a stable dependency of got. No security concern. | ai | |
| dependencies | unvetted-dep:@szmarczak/http-timer | AI (dependencies): @szmarczak/http-timer is a well-known HTTP timing utility, a stable dependency of got. No security concern. | ai | |
| dependencies | unvetted-dep:cacheable-request | AI (dependencies): cacheable-request is a well-known HTTP caching utility, a stable dependency of got. No security concern. | ai | |
| dependencies | unvetted-dep:p-cancelable | AI (dependencies): p-cancelable is a well-known sindresorhus package, a stable dependency of got across many versions. No security concern. | ai | |
| dependencies | unvetted-dep:responselike | AI (dependencies): responselike is a legitimate, established utility package used by got. No security concern. | ai | |
| dependencies | unvetted-dep:http2-wrapper | AI (dependencies): http2-wrapper is a well-known HTTP/2 utility package, a stable dependency of got. No security concern. | ai | |
| dependencies | unvetted-dep:lowercase-keys | AI (dependencies): lowercase-keys is a well-known sindresorhus utility package, a stable dependency of got. No security concern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): szmarczak was a long-time co-maintainer; sindresorhus remains publisher. Normal project evolution, not a takeover. | ai | |
| provenance | no-provenance | AI (provenance): got is a well-established package from a highly trusted publisher (sindresorhus); lack of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 15.0.5 | 12 / 40 | |
| 15.0.4 | 12 / 40 | |
| 15.0.3 | 12 / 40 | |
| 15.0.2 | 12 / 40 | |
| 15.0.1 | 12 / 40 | |
| 15.0.0 | 12 / 40 | |
| 14.6.6 | 12 / 44 | |
| 14.6.5 | 12 / 44 | |
| 14.6.4 | 12 / 44 | |
| 14.6.3 | 12 / 44 | |
| 14.6.2 | 13 / 44 | |
| 14.6.1 | 12 / 44 | |
| 14.6.0 | 12 / 43 | |
| 14.5.0 | 12 / 43 | |
| 14.4.9 | 11 / 42 | |
| 14.4.8 | 11 / 42 | |
| 14.4.7 | 11 / 42 | |
| 14.4.6 | 11 / 42 | |
| 14.4.5 | 11 / 42 | |
| 14.4.4 | 11 / 42 | |
| 14.4.3 | 11 / 42 | |
| 14.4.2 | 11 / 42 | |
| 14.4.1 | 12 / 41 | |
| 14.4.0 | 11 / 42 | |
| 14.3.0 | 11 / 41 | |
| 14.2.1 | 11 / 41 | |
| 14.2.0 | 11 / 41 | |
| 14.1.0 | 11 / 41 | |
| 14.0.0 | 11 / 41 | |
| 13.0.0 | 11 / 43 | |
| 12.6.1 | 11 / 43 | |
| 12.6.0 | 11 / 43 | |
| 12.5.3 | 11 / 44 | |
| 12.5.2 | 11 / 44 | |
| 12.5.1 | 11 / 44 | |
| 12.5.0 | 11 / 44 | |
| 12.4.1 | 12 / 43 | |
| 12.4.0 | 12 / 43 | |
| 12.3.1 | 13 / 43 | |
| 12.3.0 | 13 / 43 | |
| 12.2.0 | 13 / 43 | |
| 12.1.0 | 13 / 43 | |
| 11.8.6 | 11 / 37 | |
| 11.8.5 | 11 / 36 |
v15.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.4.1
2 findingsThis version was published by a different npm account than previous versions on 2022-09-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.