@framework-m/ui
Design system primitives for Framework M — presentational components with no business logic
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small design-system package; no provenance is low risk given clean metadata and no install scripts. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; name similarity to uuid is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; name similarity to pg is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; name similarity to qs is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; name similarity to joi is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; name similarity to yup is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:react-native-svg | AI (phantom-deps): Platform-specific peer/binary dep; not directly imported is expected for RN packages. | ai | |
| phantom-deps | phantom-dep:@tamagui/timer | AI (phantom-deps): Tamagui sub-package likely used transitively or in config; phantom-dep heuristic false positive here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 5 / 26 | |
| 0.7.2 | 5 / 26 | |
| 0.7.1 | 5 / 26 | |
| 0.7.0 | 5 / 26 | |
| 0.6.0 | 5 / 16 | |
| 0.5.0 | 2 / 15 | |
| 0.4.1 | 2 / 15 | |
| 0.4.0 | 2 / 15 | |
| 0.3.0 | 2 / 15 | |
| 0.2.5 | 1 / 15 | |
| 0.2.3 | 1 / 15 | |
| 0.2.2 | 1 / 15 |
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.