@aws-amplify/storage
Storage category of aws-amplify
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 | suspicious-version-number | AI (publish-pattern): Version 6.6.6 is a legitimate sequential release in a 2261-version package from the official AWS Amplify publisher. Repeating-digit heuristic is a stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 5 new deps (tslib, buffer, @aws-sdk/types, @smithy/md5-js, fast-xml-parser) are well-known, legitimate packages consistent with AWS S3 storage functionality. No suspicious additions. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Source size drop is consistent with modular refactoring (more files, less total code). No stub/redirect indicators present. | ai | |
| source-diff | large-new-source-files | AI (source-diff): AWS Amplify v6 modular refactor splits code into many smaller files; large file count increases are expected and consistent with the simultaneous source size reduction. | ai | |
| dependencies | unvetted-dep:@aws-sdk/client-s3-browser | AI (dependencies): Early AWS SDK v3 preview dependency used by the official AWS Amplify storage package; same AWS ecosystem, no security concern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of richardzcode is consistent with normal AWS team transitions. | ai | |
| provenance | publisher-changed | AI (provenance): Both powerful23 and mlabieniec are known AWS Amplify team members; publisher rotation is normal for this org's packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): amzn-oss, jamesiri, jpeddicord are AWS team accounts; routine team roster changes for an official AWS package. | ai | |
| provenance | no-provenance | AI (provenance): aws-amplify-ops consistently publishes without Sigstore provenance; this is expected for this publisher and package family. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of FileReader.readAsDataURL result is standard React Native file handling; no obfuscation or malicious payload present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a mature AWS Amplify subpath package entry point; minimal README/keywords and version number are expected for this package structure, not spam indicators. | ai |
Versions (showing 100 of 343)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 5 / 6 | |
| 6.0.0 | 5 / 3 | |
| 5.9.21 | 7 / 2 | |
| 5.9.20 | 7 / 2 | |
| 5.9.19 | 7 / 2 | |
| 5.9.18 | 7 / 2 | |
| 5.9.17 | 7 / 2 | |
| 5.9.16 | 7 / 2 | |
| 5.9.15 | 7 / 2 | |
| 5.9.14 | 7 / 2 | |
| 5.9.13 | 7 / 2 | |
| 5.9.12 | 7 / 2 | |
| 5.9.11 | 7 / 2 | |
| 5.9.10 | 7 / 2 | |
| 5.9.9 | 7 / 2 | |
| 5.9.8 | 7 / 2 | |
| 5.9.7 | 7 / 2 | |
| 5.9.6 | 7 / 2 | |
| 5.9.5 | 7 / 2 | |
| 5.9.4 | 7 / 2 | |
| 5.9.3 | 7 / 2 | |
| 5.9.2 | 7 / 2 | |
| 5.9.1 | 7 / 2 | |
| 5.9.0 | 6 / 2 | |
| 5.8.0 | 7 / 1 | |
| 5.7.0 | 7 / 1 | |
| 5.6.3 | 8 / 1 | |
| 5.6.2 | 8 / 1 | |
| 5.6.1 | 8 / 1 | |
| 5.6.0 | 8 / 1 | |
| 5.5.0 | 8 / 1 | |
| 5.4.1 | 8 / 1 | |
| 5.4.0 | 8 / 1 | |
| 5.3.1 | 8 / 1 | |
| 5.3.0 | 8 / 1 | |
| 5.2.6 | 8 / 1 | |
| 5.2.5 | 8 / 1 | |
| 5.2.4 | 8 / 1 | |
| 5.2.3 | 8 / 1 | |
| 5.2.2 | 8 / 1 | |
| 5.2.1 | 8 / 1 | |
| 5.2.0 | 8 / 1 | |
| 5.1.15 | 8 / 1 | |
| 5.1.14 | 8 / 1 | |
| 5.1.13 | 8 / 1 | |
| 5.1.12 | 8 / 1 | |
| 5.1.11 | 8 / 1 | |
| 5.1.10 | 8 / 1 | |
| 5.1.9 | 8 / 1 | |
| 5.1.8 | 8 / 1 | |
| 5.1.7 | 8 / 1 | |
| 5.1.6 | 8 / 1 | |
| 5.1.5 | 8 / 1 | |
| 5.1.4 | 8 / 1 | |
| 5.1.3 | 8 / 1 | |
| 5.1.2 | 8 / 1 | |
| 5.1.1 | 8 / 1 | |
| 5.1.0 | 8 / 1 | |
| 5.0.9 | 8 / 1 | |
| 5.0.8 | 8 / 1 | |
| 5.0.7 | 8 / 1 | |
| 5.0.6 | 8 / 1 | |
| 5.0.5 | 8 / 1 | |
| 5.0.4 | 8 / 1 | |
| 5.0.3 | 8 / 1 | |
| 5.0.2 | 8 / 1 | |
| 5.0.1 | 8 / 1 | |
| 5.0.0 | 8 / 1 | |
| 4.5.17 | 7 / 1 | |
| 4.5.16 | 7 / 1 | |
| 4.5.15 | 7 / 1 | |
| 4.5.14 | 7 / 1 | |
| 4.5.13 | 7 / 1 | |
| 4.5.12 | 7 / 1 | |
| 4.5.11 | 7 / 1 | |
| 4.5.10 | 7 / 1 | |
| 4.5.9 | 7 / 1 | |
| 4.5.8 | 7 / 1 | |
| 4.5.7 | 7 / 1 | |
| 4.5.6 | 7 / 1 | |
| 4.5.5 | 7 / 1 | |
| 4.5.4 | 7 / 1 | |
| 4.5.3 | 7 / 1 | |
| 4.5.2 | 7 / 1 | |
| 4.5.1 | 7 / 1 | |
| 4.5.0 | 7 / 1 | |
| 4.4.29 | 7 / 1 | |
| 4.4.28 | 7 / 1 | |
| 4.4.27 | 7 / 1 | |
| 4.4.26 | 7 / 1 | |
| 4.4.25 | 7 / 1 | |
| 4.4.24 | 7 / 1 | |
| 4.4.23 | 7 / 1 | |
| 4.4.22 | 7 / 1 | |
| 4.4.21 | 7 / 1 | |
| 4.4.20 | 7 / 1 | |
| 4.4.19 | 7 / 1 | |
| 4.4.18 | 7 / 1 | |
| 4.4.17 | 7 / 1 | |
| 4.4.16 | 7 / 1 |
v6.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.
v6.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.
v5.9.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.9.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.
v5.8.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.
v5.7.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.
v5.6.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.
v5.6.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.
v5.6.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.
v5.6.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.
v5.5.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.
v5.4.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.
v5.4.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.
v5.3.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.
v5.3.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.
v4.5.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.5.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.5.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.
v4.4.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.