@smithy/middleware-endpoint
[](https://www.npmjs.com/package/@smithy/middleware-endpoint) [](https://www.npmjs.com/packag
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper declared in dependencies; its implicit import pattern is expected for all TypeScript-compiled @smithy packages. | ai | |
| provenance | no-provenance | AI (provenance): smithy-team consistently publishes without Sigstore provenance; the publisher's track record and official GitHub repo provide sufficient trust signal. | ai |
Versions (showing 10 of 110)
| Version | Deps | Published |
|---|---|---|
| 3.1.3 | 7 / 4 | |
| 3.1.2 | 7 / 4 | |
| 3.1.1 | 7 / 4 | |
| 3.1.0 | 7 / 4 | |
| 3.0.5 | 7 / 4 | |
| 3.0.4 | 7 / 4 | |
| 3.0.3 | 7 / 4 | |
| 3.0.2 | 7 / 4 | |
| 3.0.1 | 7 / 4 | |
| 3.0.0 | 7 / 4 |
v3.1.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.1.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.1.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.1.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.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.