response-iterator
Creates an async iterator for a variety of inputs in the browser and node. Supports fetch, node-fetch, and cross-fetch
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
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 0 / 16 | |
| 1.0.10 | 0 / 15 | |
| 1.0.9 | 0 / 15 | |
| 1.0.8 | 0 / 15 | |
| 1.0.7 | 0 / 15 | |
| 1.0.6 | 0 / 15 | |
| 1.0.5 | 0 / 15 | |
| 1.0.4 | 0 / 12 | |
| 1.0.3 | 0 / 12 | |
| 1.0.2 | 0 / 12 | |
| 1.0.1 | 0 / 12 | |
| 1.0.0 | 0 / 12 | |
| 0.2.25 | 0 / 12 | |
| 0.2.24 | 0 / 12 | |
| 0.2.23 | 0 / 12 | |
| 0.2.22 | 0 / 12 | |
| 0.2.21 | 0 / 12 | |
| 0.2.20 | 0 / 12 | |
| 0.2.19 | 1 / 11 | |
| 0.2.18 | 1 / 11 | |
| 0.2.17 | 1 / 11 | |
| 0.2.16 | 1 / 11 | |
| 0.2.15 | 0 / 12 | |
| 0.2.14 | 0 / 13 | |
| 0.2.13 | 0 / 13 | |
| 0.2.11 | 0 / 13 | |
| 0.2.10 | 0 / 13 | |
| 0.2.9 | 0 / 13 | |
| 0.2.8 | 0 / 13 | |
| 0.2.7 | 0 / 13 | |
| 0.2.6 | 0 / 10 | |
| 0.2.5 | 0 / 10 | |
| 0.2.4 | 0 / 10 | |
| 0.2.3 | 0 / 10 | |
| 0.2.2 | 0 / 10 | |
| 0.2.1 | 0 / 48 | |
| 0.2.0 | 0 / 48 | |
| 0.1.1 | 0 / 45 | |
| 0.1.0 | 0 / 45 |
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.