@adaptivejs/ui
Shared declarative UI primitives for Adaptive.
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 @adaptivejs namespace; not a plausible typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @adaptivejs namespace; not a plausible typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @adaptivejs namespace; not a plausible typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @adaptivejs namespace; not a plausible typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @adaptivejs namespace; not a plausible typosquat of yup. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.1.8 | 1 / 1 | |
| 0.1.7 | 1 / 1 | |
| 0.1.6 | 1 / 1 | |
| 0.1.5 | 1 / 1 | |
| 0.1.4 | 1 / 1 | |
| 0.1.3 | 1 / 1 | |
| 0.1.2 | 1 / 1 | |
| 0.1.1 | 1 / 1 | |
| 0.1.0 | 1 / 1 |
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.