@smithy/smithy-client
[](https://www.npmjs.com/package/@smithy/smithy-client) [](https://www.npmjs.com/package/@smithy/smithy-c
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA attestation; expected for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable omission across many versions of this established AWS package. | ai | |
| phantom-deps | phantom-dep:@smithy/util-stream | AI (phantom-deps): Framework-scoped sibling package loaded by convention in the Smithy TypeScript ecosystem; not a real phantom dependency. | ai | |
| dependencies | unvetted-dep:@smithy/middleware-endpoint | AI (dependencies): Sibling @smithy namespace package published by the same smithy-team publisher; expected dependency in the Smithy TypeScript ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects mature package newly entering the registry from the smithy-typescript monorepo. Publisher track record and repo URL confirm legitimacy. | ai | |
| phantom-deps | phantom-dep:@smithy/protocol-http | AI (phantom-deps): Framework-scoped sibling package loaded by convention in the Smithy TypeScript ecosystem; not a real phantom dependency. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper declared as a dependency; phantom-dep false positive for this package. | ai |
Versions (showing 51 of 132)
| Version | Deps | Published |
|---|---|---|
| 4.14.1 | 3 / 1 | |
| 4.14.0 | 3 / 1 | |
| 4.13.7 | 3 / 1 | |
| 4.13.6 | 3 / 0 | |
| 4.13.5 | 3 / 0 | |
| 4.13.4 | 3 / 0 | |
| 4.13.3 | 3 / 0 | |
| 4.13.2 | 3 / 0 | |
| 4.13.1 | 3 / 0 | |
| 4.13.0 | 3 / 0 | |
| 4.12.13 | 7 / 5 | |
| 4.12.12 | 7 / 5 | |
| 4.12.11 | 7 / 5 | |
| 4.12.10 | 7 / 5 | |
| 4.12.9 | 7 / 5 | |
| 4.12.8 | 7 / 5 | |
| 4.12.7 | 7 / 5 | |
| 4.12.6 | 7 / 5 | |
| 4.12.5 | 7 / 5 | |
| 4.12.4 | 7 / 5 | |
| 4.12.3 | 7 / 5 | |
| 4.12.2 | 7 / 5 | |
| 4.12.1 | 7 / 5 | |
| 4.12.0 | 7 / 5 | |
| 4.11.8 | 7 / 5 | |
| 4.11.7 | 7 / 5 | |
| 4.11.6 | 7 / 5 | |
| 4.11.5 | 7 / 5 | |
| 4.11.4 | 7 / 5 | |
| 4.11.3 | 7 / 5 | |
| 4.11.2 | 7 / 5 | |
| 4.11.1 | 7 / 5 | |
| 4.11.0 | 7 / 5 | |
| 4.10.12 | 7 / 5 | |
| 4.10.11 | 7 / 5 | |
| 4.10.10 | 7 / 5 | |
| 4.10.9 | 7 / 5 | |
| 4.10.8 | 7 / 5 | |
| 4.10.7 | 7 / 5 | |
| 4.10.6 | 7 / 5 | |
| 4.10.5 | 7 / 5 | |
| 4.10.4 | 7 / 5 | |
| 4.10.3 | 7 / 5 | |
| 4.10.2 | 7 / 5 | |
| 4.10.1 | 7 / 5 | |
| 4.10.0 | 7 / 5 | |
| 4.9.10 | 7 / 5 | |
| 4.9.9 | 7 / 5 | |
| 4.9.8 | 7 / 5 | |
| 4.9.7 | 7 / 5 | |
| 4.9.6 | 7 / 5 |
v4.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.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.
v4.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.