@aws-sdk/client-elastic-load-balancing-v2
AWS SDK for JavaScript Elastic Load Balancing V2 Client for Node.js, Browser and React Native
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist-es/schemas/schemas_0.js | AI (source-diff): AWS SDK v3 schema files use short variable names as a bundle-size optimization for AWS API field names. This is a documented pattern across the SDK, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): AWS SDK v3 regularly adds schema/codegen files across versions as part of architectural evolution. Large file additions are expected for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher remains aws-sdk-bot (official AWS automation). Removed maintainers are AWS employees; routine team/maintainer list cleanup, not a takeover. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-serde | AI (phantom-deps): Framework-scoped Smithy package loaded by convention in AWS SDK v3; not a real phantom dependency risk. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-sso-oidc | AI (phantom-deps): AWS SDK v3 pattern: dependencies loaded by convention in the SDK architecture, not true phantom deps. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): AWS SDK v3 pattern: dependencies loaded by convention in the SDK architecture, not true phantom deps. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-sts | AI (phantom-deps): AWS SDK v3 pattern: dependencies loaded by convention in the SDK architecture, not true phantom deps. | ai |
Versions (showing 100 of 575)
| Version | Deps | Published |
|---|---|---|
| 3.289.0 | 37 / 8 | |
| 3.288.0 | 37 / 8 | |
| 3.287.0 | 37 / 8 | |
| 3.282.0 | 37 / 8 | |
| 3.281.0 | 37 / 8 | |
| 3.279.0 | 37 / 8 | |
| 3.278.0 | 37 / 8 | |
| 3.276.0 | 37 / 8 | |
| 3.272.0 | 37 / 8 | |
| 3.271.0 | 37 / 8 | |
| 3.267.0 | 37 / 8 | |
| 3.266.1 | 37 / 8 | |
| 3.266.0 | 37 / 8 | |
| 3.264.0 | 37 / 8 | |
| 3.262.0 | 37 / 8 | |
| 3.261.0 | 37 / 8 | |
| 3.259.0 | 37 / 8 | |
| 3.258.0 | 37 / 8 | |
| 3.257.0 | 38 / 8 | |
| 3.256.0 | 38 / 8 | |
| 3.254.0 | 38 / 8 | |
| 3.252.0 | 38 / 8 | |
| 3.245.0 | 38 / 8 | |
| 3.241.0 | 38 / 8 | |
| 3.238.0 | 38 / 8 | |
| 3.236.0 | 38 / 8 | |
| 3.235.0 | 38 / 8 | |
| 3.234.0 | 38 / 8 | |
| 3.231.0 | 38 / 8 | |
| 3.229.0 | 38 / 8 | |
| 3.226.0 | 37 / 8 | |
| 3.224.0 | 37 / 8 | |
| 3.223.0 | 37 / 8 | |
| 3.222.0 | 38 / 8 | |
| 3.218.0 | 37 / 8 | |
| 3.216.0 | 37 / 8 | |
| 3.215.0 | 37 / 8 | |
| 3.213.0 | 37 / 8 | |
| 3.212.0 | 37 / 8 | |
| 3.211.0 | 37 / 8 | |
| 3.210.0 | 37 / 8 | |
| 3.209.0 | 37 / 8 | |
| 3.204.0 | 39 / 8 | |
| 3.202.0 | 38 / 8 | |
| 3.201.0 | 38 / 8 | |
| 3.200.0 | 38 / 8 | |
| 3.199.0 | 38 / 8 | |
| 3.198.0 | 38 / 8 | |
| 3.197.0 | 38 / 8 | |
| 3.196.0 | 38 / 8 | |
| 3.194.0 | 38 / 8 | |
| 3.193.0 | 36 / 8 | |
| 3.192.0 | 36 / 8 | |
| 3.190.0 | 36 / 8 | |
| 3.188.0 | 36 / 8 | |
| 3.187.0 | 37 / 8 | |
| 3.186.0 | 37 / 8 | |
| 3.185.0 | 37 / 8 | |
| 3.183.0 | 37 / 8 | |
| 3.181.0 | 37 / 8 | |
| 3.180.0 | 37 / 8 | |
| 3.179.0 | 37 / 8 | |
| 3.178.0 | 37 / 8 | |
| 3.171.0 | 37 / 8 | |
| 3.170.0 | 37 / 8 | |
| 3.169.0 | 37 / 8 | |
| 3.168.0 | 37 / 8 | |
| 3.165.0 | 37 / 8 | |
| 3.163.0 | 37 / 8 | |
| 3.162.0 | 37 / 8 | |
| 3.161.0 | 37 / 8 | |
| 3.160.0 | 37 / 8 | |
| 3.159.0 | 37 / 8 | |
| 3.158.0 | 37 / 8 | |
| 3.154.0 | 37 / 8 | |
| 3.150.0 | 37 / 8 | |
| 3.145.0 | 37 / 8 | |
| 3.142.0 | 37 / 8 | |
| 3.141.0 | 37 / 8 | |
| 3.137.0 | 37 / 8 | |
| 3.131.0 | 37 / 8 | |
| 3.130.0 | 37 / 8 | |
| 3.128.0 | 37 / 8 | |
| 3.127.0 | 37 / 8 | |
| 3.121.0 | 37 / 8 | |
| 3.120.0 | 37 / 8 | |
| 3.118.1 | 37 / 8 | |
| 3.118.0 | 37 / 8 | |
| 3.112.0 | 37 / 8 | |
| 3.110.0 | 37 / 8 | |
| 3.109.0 | 37 / 8 | |
| 3.107.0 | 37 / 8 | |
| 3.105.0 | 37 / 8 | |
| 3.100.0 | 36 / 8 | |
| 3.99.0 | 36 / 8 | |
| 3.95.0 | 36 / 8 | |
| 3.94.0 | 36 / 8 | |
| 3.92.0 | 36 / 8 | |
| 3.87.0 | 36 / 8 | |
| 3.85.0 | 36 / 8 |
v3.289.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.288.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.287.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.282.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.281.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.279.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.278.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.276.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.272.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.271.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.267.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.266.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.266.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.262.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.261.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.259.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.258.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.257.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.256.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.254.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.252.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.245.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.241.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.238.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.236.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.235.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.234.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.231.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.229.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.226.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.224.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.223.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.222.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.209.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.204.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.202.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.201.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.200.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.199.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.198.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.197.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.196.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.194.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.193.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.192.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.190.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.188.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.187.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.186.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.185.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.183.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.181.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.180.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.179.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.178.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.171.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.170.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.169.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.168.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.165.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.163.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.162.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.161.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.160.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.159.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.158.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.154.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.150.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.145.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.142.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.141.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.137.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.131.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.130.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.127.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.118.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.118.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.109.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.