@smithy/protocol-http
[](https://www.npmjs.com/package/@smithy/protocol-http) [](https://www.npmjs.com/package/@smithy/protocol
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Smithy-team is the canonical AWS Smithy publisher; sporadic release cadence is normal for this org's packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @smithy/core is a sibling package from the same trusted org; not a suspicious third-party dep. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects intentional refactor moving code into @smithy/core, not code removal or stubbing. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.4.5 | 2 / 0 | |
| 5.4.4 | 2 / 0 | |
| 5.4.3 | 2 / 0 | |
| 5.4.2 | 2 / 0 | |
| 5.4.1 | 2 / 0 | |
| 5.4.0 | 2 / 0 | |
| 5.3.14 | 2 / 4 | |
| 5.3.13 | 2 / 4 | |
| 5.3.12 | 2 / 4 | |
| 5.3.11 | 2 / 4 | |
| 5.3.10 | 2 / 4 | |
| 5.3.9 | 2 / 4 | |
| 5.3.8 | 2 / 4 | |
| 5.3.7 | 2 / 4 | |
| 5.3.6 | 2 / 4 | |
| 5.3.5 | 2 / 4 | |
| 5.3.4 | 2 / 4 | |
| 5.3.3 | 2 / 4 | |
| 5.3.2 | 2 / 4 | |
| 5.3.1 | 2 / 4 | |
| 5.3.0 | 2 / 4 | |
| 5.2.1 | 2 / 4 | |
| 5.2.0 | 2 / 4 | |
| 5.1.3 | 2 / 4 | |
| 5.1.2 | 2 / 4 | |
| 5.1.1 | 2 / 4 |
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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.