@smithy/middleware-retry
[](https://www.npmjs.com/package/@smithy/middleware-retry) [](https://www.npmjs.com/package/@smithy
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; consistent with SLSA provenance attestation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable omission across versions of this well-established AWS SDK package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly declared in dependencies; it's a standard TypeScript runtime helper used across all @smithy packages. Not a real phantom dependency concern. | ai | |
| provenance | no-provenance | AI (provenance): smithy-team consistently publishes without Sigstore provenance across all 46 packages; this is a stable pattern for this publisher, not a per-version concern. | ai |
Versions (showing 38 of 138)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 9 / 6 | |
| 4.0.1 | 9 / 6 | |
| 4.0.0 | 9 / 6 | |
| 3.0.34 | 9 / 6 | |
| 3.0.33 | 9 / 6 | |
| 3.0.32 | 9 / 6 | |
| 3.0.31 | 9 / 6 | |
| 3.0.30 | 9 / 6 | |
| 3.0.29 | 9 / 6 | |
| 3.0.28 | 9 / 6 | |
| 3.0.27 | 9 / 6 | |
| 3.0.26 | 9 / 6 | |
| 3.0.25 | 9 / 6 | |
| 3.0.24 | 9 / 6 | |
| 3.0.23 | 9 / 6 | |
| 3.0.22 | 9 / 6 | |
| 3.0.21 | 9 / 6 | |
| 3.0.20 | 9 / 6 | |
| 3.0.19 | 9 / 6 | |
| 3.0.18 | 9 / 6 | |
| 3.0.17 | 9 / 6 | |
| 3.0.16 | 9 / 6 | |
| 3.0.15 | 9 / 6 | |
| 3.0.14 | 9 / 6 | |
| 3.0.13 | 9 / 6 | |
| 3.0.12 | 9 / 6 | |
| 3.0.11 | 9 / 6 | |
| 3.0.10 | 9 / 6 | |
| 3.0.9 | 9 / 6 | |
| 3.0.8 | 9 / 6 | |
| 3.0.7 | 9 / 6 | |
| 3.0.6 | 9 / 6 | |
| 3.0.5 | 9 / 6 | |
| 3.0.4 | 9 / 6 | |
| 3.0.3 | 9 / 6 | |
| 3.0.2 | 9 / 6 | |
| 3.0.1 | 9 / 6 | |
| 3.0.0 | 9 / 6 |
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.