@better-s3/ui
Pre-built React UI components for S3 file upload, download, and delete
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): hamidrezakz confirmed as known maintainer by email match on prior approved versions; legitimate transfer. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped S3/React UI package; no plausible impersonation of uuid. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped S3/React UI package; no plausible impersonation of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped S3/React UI package; no plausible impersonation of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped S3/React UI package; no plausible impersonation of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped S3/React UI package; no plausible impersonation of yup. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.1048.0 | 1 / 12 | |
| 3.1047.0 | 1 / 12 | |
| 3.1046.0 | 1 / 12 | |
| 3.1045.2 | 1 / 12 | |
| 3.1045.1 | 1 / 11 | |
| 3.1045.0 | 1 / 11 | |
| 3.1044.0 | 1 / 11 | |
| 3.3.0 | 1 / 11 | |
| 3.2.1 | 1 / 11 | |
| 3.2.0 | 1 / 11 | |
| 3.1.1 | 1 / 11 | |
| 3.1.0 | 1 / 11 | |
| 3.0.0 | 1 / 11 | |
| 2.3.1 | 1 / 11 | |
| 2.3.0 | 1 / 11 | |
| 2.2.0 | 1 / 11 | |
| 2.1.0 | 1 / 11 | |
| 2.0.0 | 1 / 11 | |
| 1.0.0 | 2 / 11 |
v3.1048.0
3 findingsAll previous maintainers (houk) were replaced by new maintainers (hamidrezakz). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hamidrezakz) than the most recent previously approved version (houk) on 2026-05-31, but hamidrezakz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1047.0
3 findingsAll previous maintainers (houk) were replaced by new maintainers (hamidrezakz). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (hamidrezakz) than the most recent previously approved version (houk) on 2026-05-30, but hamidrezakz is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1046.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1045.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1045.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1045.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1044.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.