@crawlee/impit-client
impit-based HTTP client implementation for Crawlee. Impersonates browser requests to avoid bot detection.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 3 / 1 | |
| 3.16.0 | 3 / 1 | |
| 3.15.3 | 3 / 1 | |
| 3.15.2 | 3 / 1 | |
| 3.15.1 | 3 / 1 | |
| 3.15.0 | 3 / 1 | |
| 3.14.1 | 3 / 1 | |
| 3.14.0 | 3 / 1 | |
| 3.13.10 | 3 / 1 | |
| 3.13.9 | 3 / 1 | |
| 3.13.8 | 3 / 1 | |
| 3.13.7 | 3 / 1 | |
| 3.13.6 | 3 / 1 | |
| 3.13.5 | 2 / 1 | |
| 3.13.4 | 2 / 1 | |
| 3.13.3 | 1 / 1 |
v3.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.