@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 |
|---|---|---|
| 4.4.15 | 8 / 1 | |
| 4.4.14 | 8 / 1 | |
| 4.4.13 | 8 / 1 | |
| 4.4.12 | 8 / 1 | |
| 4.4.11 | 8 / 1 | |
| 4.4.10 | 8 / 1 | |
| 4.4.9 | 8 / 1 | |
| 4.4.8 | 8 / 1 | |
| 4.4.7 | 8 / 1 | |
| 4.4.6 | 8 / 1 | |
| 4.4.5 | 8 / 1 | |
| 4.4.4 | 8 / 1 | |
| 4.4.3 | 8 / 1 | |
| 4.4.2 | 8 / 1 | |
| 4.4.1 | 8 / 1 | |
| 4.4.0 | 8 / 1 | |
| 4.3.11 | 8 / 1 | |
| 4.3.10 | 8 / 1 | |
| 4.3.9 | 8 / 1 | |
| 4.3.8 | 8 / 1 | |
| 4.3.7 | 8 / 1 | |
| 4.3.6 | 8 / 1 | |
| 4.3.5 | 8 / 1 | |
| 4.3.4 | 8 / 1 | |
| 4.3.3 | 8 / 1 | |
| 4.3.2 | 8 / 1 | |
| 4.3.1 | 8 / 1 | |
| 4.3.0 | 8 / 1 | |
| 4.2.1 | 8 / 1 | |
| 4.2.0 | 8 / 1 | |
| 4.1.1 | 8 / 1 | |
| 4.1.0 | 8 / 1 | |
| 4.0.0 | 8 / 1 | |
| 3.4.4 | 8 / 1 | |
| 3.4.3 | 8 / 1 | |
| 3.4.2 | 8 / 1 | |
| 3.4.1 | 8 / 1 | |
| 3.4.0 | 8 / 1 | |
| 3.3.29 | 8 / 1 | |
| 3.3.28 | 8 / 1 | |
| 3.3.27 | 8 / 1 | |
| 3.3.26 | 8 / 1 | |
| 3.3.25 | 8 / 1 | |
| 3.3.24 | 8 / 1 | |
| 3.3.23 | 8 / 1 | |
| 3.3.22 | 8 / 1 | |
| 3.3.21 | 8 / 1 | |
| 3.3.20 | 8 / 1 | |
| 3.3.19 | 8 / 1 | |
| 3.3.18 | 8 / 1 | |
| 3.3.17 | 8 / 1 | |
| 3.3.16 | 8 / 1 | |
| 3.3.15 | 8 / 1 | |
| 3.3.14 | 8 / 1 | |
| 3.3.13 | 8 / 1 | |
| 3.3.12 | 8 / 1 | |
| 3.3.11 | 8 / 1 | |
| 3.3.10 | 8 / 1 | |
| 3.3.9 | 8 / 1 | |
| 3.3.8 | 8 / 1 | |
| 3.3.7 | 8 / 1 | |
| 3.3.6 | 8 / 1 | |
| 3.3.5 | 8 / 1 | |
| 3.3.4 | 8 / 1 | |
| 3.3.3 | 8 / 1 | |
| 3.3.2 | 8 / 1 | |
| 3.3.1 | 8 / 1 | |
| 3.3.0 | 8 / 1 | |
| 3.2.14 | 8 / 1 | |
| 3.2.13 | 8 / 1 | |
| 3.2.12 | 8 / 1 | |
| 3.2.11 | 8 / 1 | |
| 3.2.10 | 8 / 1 | |
| 3.2.9 | 8 / 1 | |
| 3.2.8 | 8 / 1 | |
| 3.2.7 | 8 / 1 | |
| 3.2.6 | 8 / 1 | |
| 3.2.5 | 8 / 1 | |
| 3.2.4 | 8 / 1 | |
| 3.2.3 | 8 / 1 | |
| 3.2.2 | 8 / 1 | |
| 3.2.1 | 8 / 1 | |
| 3.2.0 | 8 / 1 | |
| 3.1.9 | 8 / 1 | |
| 3.1.8 | 8 / 1 | |
| 3.1.7 | 8 / 1 | |
| 3.1.6 | 8 / 1 | |
| 3.1.5 | 8 / 1 | |
| 3.1.4 | 8 / 1 | |
| 3.1.3 | 7 / 1 | |
| 3.1.2 | 7 / 1 | |
| 3.1.0 | 7 / 1 | |
| 2.2.3 | 1 / 0 | |
| 2.2.2 | 1 / 0 | |
| 2.2.1 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.3 | 1 / 0 | |
| 2.1.2 | 1 / 0 | |
| 2.1.1 | 1 / 0 | |
| 2.1.0 | 1 / 0 |
v4.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.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.
v4.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.
v4.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.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.
v4.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.
v4.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.
v4.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.
v4.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.
v4.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.
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.4.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.4.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.4.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.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.
v3.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.
v3.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.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.
v3.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.
v3.2.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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
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.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.