@aws-sdk/middleware-websocket
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): aws-sdk-bot is the canonical AWS SDK automation account with 34k+ approved packages; dormancy in a stable middleware package followed by a routine update is not a takeover signal. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard implicit dependency in AWS SDK monorepo packages; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): Framework-scoped AWS SDK types package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/util-utf8 | AI (phantom-deps): First-party Smithy utility package loaded by convention in the AWS SDK monorepo; stable false positive. | ai |
Versions (showing 6 of 106)
| Version | Deps | Published |
|---|---|---|
| 3.582.0 | 11 / 9 | |
| 3.577.0 | 11 / 9 | |
| 3.575.0 | 11 / 9 | |
| 3.572.0 | 11 / 9 | |
| 3.569.0 | 11 / 9 | |
| 3.567.0 | 11 / 9 |
v3.582.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.577.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.575.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.572.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.569.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.567.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.