@smithy/fetch-http-handler
Provides a way to make requests
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a runtime implicit dep used by TypeScript compilation; stable false positive. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): This package IS an HTTP handler — fetch() is its core functionality, not telemetry or exfiltration. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects migration from a larger AWS SDK package, not spam. Part of the established smithy-team publisher ecosystem. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 5.5.1 | 3 / 5 | |
| 5.5.0 | 3 / 5 | |
| 5.4.7 | 3 / 5 | |
| 5.4.6 | 3 / 5 | |
| 5.4.5 | 3 / 5 | |
| 5.4.4 | 3 / 5 | |
| 5.4.3 | 3 / 5 | |
| 5.4.2 | 3 / 5 | |
| 5.4.1 | 3 / 5 | |
| 5.4.0 | 3 / 5 | |
| 5.3.17 | 5 / 5 | |
| 5.3.16 | 5 / 5 | |
| 5.3.15 | 5 / 5 | |
| 5.3.14 | 5 / 5 | |
| 5.3.13 | 5 / 5 | |
| 5.3.12 | 5 / 5 | |
| 5.3.11 | 5 / 5 | |
| 5.3.10 | 5 / 5 | |
| 5.3.9 | 5 / 5 | |
| 5.3.8 | 5 / 5 | |
| 5.3.7 | 5 / 5 | |
| 5.3.6 | 5 / 5 | |
| 5.3.5 | 5 / 5 | |
| 5.3.4 | 5 / 5 | |
| 5.3.3 | 5 / 5 | |
| 5.3.2 | 5 / 5 | |
| 5.3.1 | 5 / 5 | |
| 5.3.0 | 5 / 5 | |
| 5.2.1 | 5 / 5 | |
| 5.2.0 | 5 / 5 | |
| 5.1.1 | 5 / 5 | |
| 5.1.0 | 5 / 5 | |
| 5.0.4 | 5 / 5 | |
| 5.0.3 | 5 / 5 | |
| 5.0.2 | 5 / 5 | |
| 5.0.1 | 5 / 5 | |
| 5.0.0 | 5 / 5 |
v5.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.6
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
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.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.