@aws-sdk/util-utf8-browser
A browser UTF-8 string <-> UInt8Array converter
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-cjs/pureJs.js | AI (source-diff): Long lines are TypeScript-compiled UTF-8 codec logic with inline binary literals — not obfuscated or malicious. Stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist-es/pureJs.js | AI (source-diff): Long lines are TypeScript-compiled UTF-8 codec logic with inline binary literals — not obfuscated or malicious. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known TypeScript runtime helper; implicit dependency is expected for TypeScript-compiled AWS SDK packages. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.259.0 | 1 / 6 | |
| 3.188.0 | 1 / 6 | |
| 3.186.0 | 1 / 6 | |
| 3.183.0 | 1 / 6 | |
| 3.170.0 | 1 / 6 | |
| 3.168.0 | 1 / 6 | |
| 3.109.0 | 1 / 6 | |
| 3.55.0 | 1 / 6 | |
| 3.52.0 | 1 / 6 | |
| 3.49.0 | 1 / 6 | |
| 3.47.1 | 1 / 0 | |
| 3.47.0 | 1 / 0 | |
| 3.46.0 | 1 / 0 | |
| 3.37.0 | 1 / 3 | |
| 3.36.0 | 1 / 3 | |
| 3.35.0 | 1 / 3 | |
| 3.34.0 | 1 / 3 | |
| 3.32.0 | 1 / 3 | |
| 3.29.0 | 1 / 3 | |
| 3.23.0 | 1 / 3 | |
| 3.22.0 | 1 / 3 | |
| 3.20.0 | 1 / 3 | |
| 3.18.0 | 1 / 3 | |
| 3.13.1 | 1 / 3 | |
| 3.12.0 | 1 / 3 | |
| 3.10.0 | 1 / 3 | |
| 3.6.1 | 1 / 3 | |
| 3.4.1 | 1 / 3 | |
| 3.4.0 | 1 / 3 | |
| 3.1.0 | 1 / 3 | |
| 3.0.0 | 1 / 3 |
v3.188.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.186.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.183.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.170.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.168.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v3.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.