@mars-stack/ui
Design-token-driven UI components and styles for MARS apps.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @mars-stack/ui is a scoped UI library, not a typosquat of uuid. Levenshtein distance on scoped package names vs. short unrelated packages is a systematic false positive here. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @mars-stack/ui is a scoped UI library, not a typosquat of pg. Edit distance of 2 from a 2-char package name is meaningless for a scoped package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @mars-stack/ui is a scoped UI library, not a typosquat of qs. Edit distance of 2 from a 2-char package name is meaningless for a scoped package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @mars-stack/ui is a scoped UI library, not a typosquat of joi. No naming similarity in intent or function. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @mars-stack/ui is a scoped UI library, not a typosquat of yup. No naming similarity in intent or function. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 13.1.9 | 0 / 14 | |
| 13.1.8 | 0 / 14 | |
| 13.1.7 | 0 / 14 | |
| 13.1.4 | 0 / 14 | |
| 13.1.3 | 0 / 14 | |
| 13.1.2 | 0 / 14 | |
| 13.0.1 | 0 / 14 | |
| 13.0.0 | 0 / 14 | |
| 11.0.2 | 0 / 14 | |
| 11.0.1 | 0 / 14 | |
| 11.0.0 | 0 / 14 | |
| 10.0.0 | 0 / 14 | |
| 9.0.10 | 0 / 14 | |
| 9.0.9 | 0 / 14 | |
| 9.0.8 | 0 / 14 | |
| 9.0.7 | 0 / 14 | |
| 9.0.6 | 0 / 14 | |
| 9.0.5 | 0 / 14 | |
| 9.0.4 | 0 / 14 | |
| 9.0.3 | 0 / 14 | |
| 9.0.2 | 0 / 14 | |
| 9.0.1 | 0 / 14 | |
| 9.0.0 | 0 / 14 | |
| 8.0.37 | 0 / 14 | |
| 8.0.36 | 0 / 14 | |
| 8.0.35 | 0 / 14 | |
| 8.0.34 | 0 / 14 | |
| 8.0.33 | 0 / 14 | |
| 8.0.32 | 0 / 14 | |
| 8.0.31 | 0 / 14 | |
| 8.0.30 | 0 / 14 | |
| 8.0.29 | 0 / 14 | |
| 8.0.28 | 0 / 14 | |
| 8.0.27 | 0 / 14 | |
| 8.0.26 | 0 / 14 | |
| 8.0.25 | 0 / 14 | |
| 8.0.24 | 0 / 14 | |
| 8.0.23 | 0 / 14 | |
| 8.0.22 | 0 / 14 | |
| 8.0.21 | 0 / 14 | |
| 8.0.20 | 0 / 14 | |
| 8.0.19 | 0 / 14 | |
| 8.0.18 | 0 / 14 | |
| 8.0.17 | 0 / 14 | |
| 8.0.16 | 0 / 14 | |
| 8.0.15 | 0 / 14 | |
| 8.0.14 | 0 / 14 | |
| 8.0.13 | 0 / 14 | |
| 8.0.12 | 0 / 14 | |
| 8.0.11 | 0 / 14 | |
| 8.0.10 | 0 / 14 |
v13.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.