@aws-amplify/codegen-ui-react
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/lib/utils-file-functions/string-formatter.d.ts | AI (source-diff): Long line is a readable exported code-template string, not obfuscation. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.20.5 | 6 / 12 | |
| 2.20.4 | 6 / 12 | |
| 2.20.3 | 6 / 12 | |
| 2.20.2 | 6 / 12 | |
| 2.14.2 | 4 / 9 |
v2.20.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aws-amplify-ops) than the most recent previously approved version (amplify-studio-uibuilder) on 2026-06-26, but aws-amplify-ops is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.20.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.