@blocklet/labels
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:unstated-next | AI (dependencies): Well-known React state management library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@iconify/icons-mdi | AI (dependencies): Standard iconify icon set; legitimate UI dependency. | ai | |
| dependencies | unvetted-dep:performant-array-to-tree | AI (dependencies): Known utility library; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@iconify/icons-material-symbols | AI (dependencies): Standard iconify icon set; legitimate UI dependency. | ai | |
| phantom-deps | phantom-dep:react-color | AI (phantom-deps): Declared as runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/css | AI (phantom-deps): Declared as runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Declared as runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Declared as runtime dep in package.json; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@blocklet/translation-input | AI (phantom-deps): Same org sibling package declared as runtime dep; phantom-dep heuristic false positive. | ai |
Versions (showing 100 of 345)
| Version | Deps | Published |
|---|---|---|
| 2.4.44 | 14 / 24 | |
| 2.4.43 | 14 / 24 | |
| 2.4.42 | 14 / 24 | |
| 2.4.41 | 14 / 24 | |
| 2.4.40 | 14 / 24 | |
| 2.4.39 | 12 / 25 | |
| 2.4.38 | 12 / 25 | |
| 2.4.37 | 12 / 25 | |
| 2.4.36 | 12 / 24 | |
| 2.4.35 | 12 / 24 | |
| 2.4.34 | 12 / 24 | |
| 2.4.33 | 12 / 24 | |
| 2.4.32 | 12 / 24 | |
| 2.4.31 | 12 / 24 | |
| 2.4.30 | 12 / 24 | |
| 2.4.29 | 12 / 24 | |
| 2.4.28 | 12 / 24 | |
| 2.4.27 | 12 / 24 | |
| 2.4.26 | 12 / 24 | |
| 2.4.25 | 12 / 24 | |
| 2.4.24 | 12 / 24 | |
| 2.4.23 | 12 / 24 | |
| 2.4.22 | 12 / 24 | |
| 2.4.21 | 12 / 24 | |
| 2.4.20 | 12 / 24 | |
| 2.4.19 | 12 / 24 | |
| 2.4.18 | 12 / 24 | |
| 2.4.17 | 12 / 24 | |
| 2.4.16 | 12 / 24 | |
| 2.4.15 | 12 / 24 | |
| 2.4.14 | 12 / 24 | |
| 2.4.13 | 12 / 24 | |
| 2.4.12 | 12 / 24 | |
| 2.4.11 | 12 / 24 | |
| 2.4.10 | 12 / 24 | |
| 2.4.9 | 12 / 24 | |
| 2.4.8 | 12 / 24 | |
| 2.4.7 | 12 / 24 | |
| 2.4.6 | 12 / 24 | |
| 2.4.5 | 12 / 24 | |
| 2.4.4 | 12 / 24 | |
| 2.4.3 | 12 / 24 | |
| 2.4.2 | 12 / 24 | |
| 2.4.1 | 12 / 24 | |
| 2.4.0 | 12 / 24 | |
| 2.3.106 | 12 / 24 | |
| 2.3.105 | 12 / 24 | |
| 2.3.104 | 12 / 24 | |
| 2.3.103 | 12 / 24 | |
| 2.3.102 | 12 / 24 | |
| 2.3.101 | 12 / 24 | |
| 2.3.100 | 12 / 24 | |
| 2.3.99 | 12 / 24 | |
| 2.3.98 | 12 / 24 | |
| 2.3.97 | 12 / 24 | |
| 2.3.96 | 12 / 24 | |
| 2.3.95 | 12 / 24 | |
| 2.3.94 | 12 / 24 | |
| 2.3.93 | 12 / 24 | |
| 2.3.92 | 12 / 24 | |
| 2.3.91 | 12 / 24 | |
| 2.3.90 | 12 / 24 | |
| 2.3.89 | 12 / 24 | |
| 2.3.88 | 12 / 24 | |
| 2.3.87 | 12 / 24 | |
| 2.3.86 | 12 / 24 | |
| 2.3.85 | 12 / 24 | |
| 2.3.84 | 12 / 24 | |
| 2.3.83 | 12 / 24 | |
| 2.3.82 | 12 / 24 | |
| 2.3.81 | 12 / 24 | |
| 2.3.80 | 12 / 24 | |
| 2.3.79 | 12 / 24 | |
| 2.3.78 | 12 / 24 | |
| 2.3.77 | 12 / 24 | |
| 2.3.76 | 12 / 24 | |
| 2.3.75 | 12 / 24 | |
| 2.3.74 | 12 / 24 | |
| 2.3.73 | 12 / 24 | |
| 2.3.72 | 12 / 24 | |
| 2.3.71 | 12 / 24 | |
| 2.3.70 | 12 / 24 | |
| 2.3.69 | 12 / 24 | |
| 2.3.68 | 12 / 24 | |
| 2.3.67 | 12 / 24 | |
| 2.3.66 | 12 / 24 | |
| 2.3.65 | 12 / 24 | |
| 2.3.64 | 12 / 24 | |
| 2.3.63 | 12 / 24 | |
| 2.3.62 | 12 / 24 | |
| 2.3.61 | 12 / 24 | |
| 2.3.60 | 12 / 24 | |
| 2.3.59 | 12 / 24 | |
| 2.3.58 | 12 / 24 | |
| 2.3.57 | 12 / 24 | |
| 2.3.56 | 12 / 24 | |
| 2.3.55 | 12 / 24 | |
| 2.3.54 | 12 / 24 | |
| 2.3.53 | 12 / 24 | |
| 2.3.52 | 12 / 24 |
v2.4.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.