@buildeross/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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @buildeross/ui package; Levenshtein match to short package names is a false positive for this scoped namespace. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same false positive pattern — scoped UI library, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same false positive pattern — scoped UI library, not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same false positive pattern — scoped UI library, not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Same false positive pattern — scoped UI library, not a typosquat of yup. | ai | |
| phantom-deps | phantom-dep:@vanilla-extract/css | AI (phantom-deps): @vanilla-extract/css is used in config files (vite/esbuild plugins) rather than direct imports; stable false positive for this build setup. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 16 / 29 | |
| 0.3.1 | 16 / 29 | |
| 0.2.2 | 11 / 28 | |
| 0.2.1 | 11 / 28 | |
| 0.2.0 | 11 / 28 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.