@blocklet/ui-react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@blocklet/sdk | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:p-all | AI (phantom-deps): Large component library; dep likely used in build/config context, stable FP. | ai | |
| phantom-deps | phantom-dep:js-cookie | AI (phantom-deps): Same pattern — config-referenced dep in a large UI library, stable FP. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Type-only usage common in TS projects; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@blocklet/constant | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly, stable FP. | ai | |
| phantom-deps | phantom-dep:iconify-icons-material-symbols-400 | AI (phantom-deps): Icon set dep referenced via config/alias; stable FP for this UI library. | ai |
Versions (showing 54 of 154)
| Version | Deps | Published |
|---|---|---|
| 3.1.11 | 35 / 7 | |
| 3.1.10 | 35 / 7 | |
| 3.1.9 | 35 / 7 | |
| 3.1.8 | 35 / 7 | |
| 3.1.7 | 35 / 7 | |
| 3.1.6 | 35 / 7 | |
| 3.1.5 | 35 / 7 | |
| 3.1.4 | 35 / 7 | |
| 3.1.3 | 35 / 7 | |
| 3.1.2 | 35 / 7 | |
| 3.1.1 | 35 / 7 | |
| 3.1.0 | 35 / 7 | |
| 3.0.43 | 35 / 6 | |
| 3.0.42 | 35 / 6 | |
| 3.0.41 | 35 / 6 | |
| 3.0.39 | 35 / 6 | |
| 3.0.38 | 35 / 6 | |
| 3.0.37 | 35 / 6 | |
| 3.0.36 | 35 / 6 | |
| 3.0.35 | 34 / 6 | |
| 3.0.34 | 34 / 6 | |
| 3.0.33 | 34 / 6 | |
| 3.0.32 | 34 / 6 | |
| 3.0.31 | 34 / 6 | |
| 3.0.30 | 34 / 6 | |
| 3.0.29 | 34 / 6 | |
| 3.0.28 | 34 / 6 | |
| 3.0.27 | 34 / 6 | |
| 3.0.26 | 34 / 6 | |
| 3.0.25 | 34 / 6 | |
| 3.0.24 | 34 / 6 | |
| 3.0.23 | 34 / 6 | |
| 3.0.22 | 34 / 6 | |
| 3.0.21 | 34 / 6 | |
| 3.0.20 | 34 / 6 | |
| 3.0.19 | 34 / 6 | |
| 3.0.17 | 34 / 6 | |
| 3.0.16 | 34 / 6 | |
| 3.0.15 | 34 / 6 | |
| 3.0.14 | 34 / 6 | |
| 3.0.13 | 34 / 6 | |
| 3.0.12 | 34 / 6 | |
| 3.0.11 | 34 / 6 | |
| 3.0.10 | 34 / 6 | |
| 3.0.9 | 34 / 6 | |
| 3.0.8 | 34 / 6 | |
| 3.0.7 | 34 / 6 | |
| 3.0.6 | 34 / 5 | |
| 3.0.5 | 34 / 5 | |
| 3.0.4 | 34 / 5 | |
| 3.0.3 | 34 / 5 | |
| 3.0.2 | 34 / 5 | |
| 3.0.1 | 34 / 5 | |
| 3.0.0 | 35 / 5 |
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.