@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 100 of 153)
| Version | Deps | Published |
|---|---|---|
| 3.5.3 | 35 / 13 | |
| 3.5.2 | 34 / 13 | |
| 3.5.1 | 34 / 13 | |
| 3.5.0 | 34 / 13 | |
| 3.4.15 | 34 / 13 | |
| 3.4.14 | 34 / 13 | |
| 3.4.13 | 34 / 13 | |
| 3.4.12 | 34 / 13 | |
| 3.4.11 | 34 / 13 | |
| 3.4.10 | 34 / 13 | |
| 3.4.9 | 34 / 13 | |
| 3.4.8 | 34 / 13 | |
| 3.4.7 | 33 / 13 | |
| 3.4.6 | 33 / 13 | |
| 3.4.5 | 33 / 13 | |
| 3.4.4 | 33 / 13 | |
| 3.4.3 | 33 / 13 | |
| 3.4.2 | 33 / 13 | |
| 3.4.1 | 33 / 13 | |
| 3.4.0 | 33 / 13 | |
| 3.3.10 | 33 / 13 | |
| 3.3.9 | 33 / 13 | |
| 3.3.8 | 33 / 13 | |
| 3.3.7 | 33 / 13 | |
| 3.3.6 | 33 / 13 | |
| 3.3.5 | 33 / 13 | |
| 3.3.4 | 33 / 13 | |
| 3.3.3 | 33 / 13 | |
| 3.3.2 | 33 / 13 | |
| 3.3.1 | 33 / 13 | |
| 3.3.0 | 33 / 13 | |
| 3.2.19 | 33 / 13 | |
| 3.2.18 | 33 / 13 | |
| 3.2.17 | 33 / 7 | |
| 3.2.16 | 33 / 7 | |
| 3.2.15 | 33 / 7 | |
| 3.2.14 | 34 / 7 | |
| 3.2.13 | 34 / 7 | |
| 3.2.12 | 34 / 7 | |
| 3.2.11 | 34 / 7 | |
| 3.2.10 | 34 / 7 | |
| 3.2.9 | 34 / 7 | |
| 3.2.8 | 34 / 7 | |
| 3.2.7 | 34 / 7 | |
| 3.2.6 | 34 / 7 | |
| 3.2.5 | 34 / 7 | |
| 3.2.4 | 34 / 7 | |
| 3.2.3 | 34 / 7 | |
| 3.2.2 | 34 / 7 | |
| 3.2.1 | 34 / 7 | |
| 3.2.0 | 34 / 7 | |
| 3.1.60 | 34 / 7 | |
| 3.1.59 | 34 / 7 | |
| 3.1.58 | 34 / 7 | |
| 3.1.57 | 34 / 7 | |
| 3.1.56 | 34 / 7 | |
| 3.1.55 | 34 / 7 | |
| 3.1.54 | 34 / 7 | |
| 3.1.53 | 34 / 7 | |
| 3.1.52 | 34 / 7 | |
| 3.1.51 | 34 / 7 | |
| 3.1.50 | 34 / 7 | |
| 3.1.49 | 34 / 7 | |
| 3.1.48 | 34 / 7 | |
| 3.1.47 | 34 / 7 | |
| 3.1.46 | 34 / 7 | |
| 3.1.45 | 34 / 7 | |
| 3.1.44 | 34 / 7 | |
| 3.1.43 | 34 / 7 | |
| 3.1.42 | 34 / 7 | |
| 3.1.41 | 34 / 7 | |
| 3.1.40 | 34 / 7 | |
| 3.1.39 | 34 / 7 | |
| 3.1.38 | 34 / 7 | |
| 3.1.37 | 34 / 7 | |
| 3.1.36 | 34 / 7 | |
| 3.1.35 | 34 / 7 | |
| 3.1.34 | 34 / 7 | |
| 3.1.33 | 34 / 7 | |
| 3.1.32 | 34 / 7 | |
| 3.1.31 | 34 / 7 | |
| 3.1.30 | 34 / 7 | |
| 3.1.28 | 35 / 7 | |
| 3.1.27 | 35 / 7 | |
| 3.1.26 | 35 / 7 | |
| 3.1.25 | 35 / 7 | |
| 3.1.24 | 35 / 7 | |
| 3.1.23 | 35 / 7 | |
| 3.1.22 | 35 / 7 | |
| 3.1.21 | 35 / 7 | |
| 3.1.20 | 35 / 7 | |
| 3.1.19 | 35 / 7 | |
| 3.1.18 | 35 / 7 | |
| 3.1.17 | 35 / 7 | |
| 3.1.16 | 35 / 7 | |
| 3.1.15 | 35 / 7 | |
| 3.1.14 | 35 / 7 | |
| 3.1.13 | 35 / 7 | |
| 3.1.12 | 35 / 7 | |
| 3.1.11 | 35 / 7 |
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.