@arthur2079/ui
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a declared runtime dependency; phantom-dep false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard minified ESM bundle output; content is readable i18n/React code, not malicious obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation — legitimate CI/CD automation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; Levenshtein match to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; Levenshtein match to uuid is coincidental, not impersonation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo UI package; missing metadata is expected for private-scope packages. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; Levenshtein match to yup is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; Levenshtein match to pg is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; Levenshtein match to qs is coincidental. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.7.6 | 2 / 7 | |
| 5.7.5 | 2 / 7 | |
| 5.5.5 | 2 / 7 | |
| 3.31.0 | 2 / 7 | |
| 3.30.1 | 2 / 7 | |
| 3.30.0 | 2 / 7 | |
| 3.29.0 | 2 / 7 | |
| 3.28.0 | 2 / 7 | |
| 3.27.3 | 2 / 7 | |
| 3.27.2 | 2 / 7 | |
| 3.27.1 | 2 / 7 | |
| 3.27.0 | 2 / 7 | |
| 3.26.1 | 2 / 7 | |
| 3.26.0 | 2 / 7 | |
| 3.25.0 | 2 / 7 | |
| 2.25.0 | 2 / 7 | |
| 1.23.0 | 2 / 7 | |
| 1.22.0 | 2 / 7 | |
| 1.21.0 | 2 / 7 | |
| 1.20.6 | 2 / 7 | |
| 0.63.1 | 12 / 14 | |
| 0.20.6 | 2 / 7 | |
| 0.20.5 | 2 / 7 | |
| 0.20.3 | 2 / 7 | |
| 0.20.2 | 2 / 7 | |
| 0.20.0 | 2 / 7 |
v5.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arthur2079.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.1
3 findingsThis version was published by a different npm account than previous versions on 2026-06-03. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arthur2079.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: arthur2079.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.