@aws-amplify/ui-react-liveness
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): AWS org housekeeping; publisher aws-amplify-ops has 4119 approved packages and long track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): uuid is a well-established package replacing nanoid; routine dep swap for this AWS Amplify component. | ai | |
| dependencies | unvetted-peer-dep:aws-amplify | AI (dependencies): Peer dependency on aws-amplify is expected for this AWS Amplify UI component. | ai | |
| dependencies | unvetted-dep:@tensorflow-models/face-detection | AI (dependencies): Official TensorFlow.js face detection model; expected dependency for a face liveness detection component. | ai | |
| phantom-deps | phantom-dep:@tensorflow/tfjs-converter | AI (phantom-deps): tfjs-converter is a declared runtime dep used by TensorFlow model loading; stable false positive for this ML-based package. | ai | |
| dependencies | unvetted-dep:@tensorflow/tfjs-core | AI (dependencies): TensorFlow.js core is a legitimate Google ML library used for face detection in this liveness component. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established AWS Amplify UI component; sparse README/keywords are a documentation issue, not a spam signal. | ai | |
| phantom-deps | phantom-dep:@mediapipe/face_detection | AI (phantom-deps): Declared as runtime dep and used via config/indirect import; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.6.5 | 18 / 9 | |
| 3.6.4 | 18 / 9 | |
| 3.6.3 | 18 / 9 | |
| 3.6.2 | 18 / 9 | |
| 3.6.1 | 18 / 9 | |
| 3.6.0 | 18 / 9 | |
| 3.5.1 | 18 / 9 | |
| 3.5.0 | 19 / 7 | |
| 3.4.7 | 19 / 7 | |
| 3.4.6 | 19 / 7 | |
| 3.4.5 | 19 / 7 | |
| 3.4.4 | 19 / 7 | |
| 3.4.3 | 19 / 7 | |
| 3.4.2 | 19 / 7 | |
| 3.4.1 | 19 / 7 | |
| 3.4.0 | 19 / 7 | |
| 3.3.9 | 19 / 7 |
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.