@blocklet/code-editor
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:monaco-vim | AI (dependencies): monaco-vim is a legitimate Vim keybinding extension for Monaco editor; expected dep for a code editor package. | ai | |
| dependencies | unvetted-dep:@iconify-icon/react | AI (dependencies): Well-known icon library; no security concern. | ai | |
| dependencies | unvetted-dep:@iconify-icons/tabler | AI (dependencies): Tabler icon set from iconify; no security concern. | ai | |
| phantom-deps | phantom-dep:joi | AI (phantom-deps): Declared in package.json, referenced in config; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ufo | AI (phantom-deps): Declared in package.json, referenced in config; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared in package.json, referenced in config; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): Declared in package.json, referenced in config; heuristic false positive for this package. | ai |
Versions (showing 100 of 283)
| Version | Deps | Published |
|---|---|---|
| 0.7.13 | 18 / 25 | |
| 0.7.12 | 18 / 25 | |
| 0.7.11 | 18 / 25 | |
| 0.7.8 | 18 / 25 | |
| 0.7.7 | 18 / 25 | |
| 0.7.6 | 18 / 25 | |
| 0.7.5 | 18 / 25 | |
| 0.7.4 | 18 / 25 | |
| 0.7.3 | 18 / 25 | |
| 0.7.2 | 18 / 25 | |
| 0.7.1 | 18 / 25 | |
| 0.7.0 | 18 / 25 | |
| 0.6.3 | 18 / 25 | |
| 0.6.2 | 18 / 25 | |
| 0.6.1 | 18 / 25 | |
| 0.6.0 | 18 / 25 | |
| 0.5.26 | 18 / 25 | |
| 0.5.25 | 18 / 25 | |
| 0.5.24 | 18 / 25 | |
| 0.5.23 | 18 / 25 | |
| 0.5.22 | 18 / 25 | |
| 0.5.21 | 18 / 25 | |
| 0.5.20 | 18 / 25 | |
| 0.5.19 | 18 / 25 | |
| 0.5.18 | 18 / 25 | |
| 0.5.17 | 18 / 25 | |
| 0.5.16 | 18 / 25 | |
| 0.5.15 | 18 / 25 | |
| 0.5.14 | 18 / 25 | |
| 0.5.13 | 18 / 25 | |
| 0.5.12 | 18 / 25 | |
| 0.5.11 | 18 / 25 | |
| 0.5.10 | 18 / 25 | |
| 0.5.9 | 18 / 25 | |
| 0.5.8 | 18 / 25 | |
| 0.5.7 | 18 / 25 | |
| 0.5.6 | 18 / 25 | |
| 0.5.5 | 18 / 25 | |
| 0.5.4 | 18 / 25 | |
| 0.5.3 | 18 / 25 | |
| 0.5.2 | 18 / 25 | |
| 0.5.1 | 18 / 25 | |
| 0.5.0 | 18 / 25 | |
| 0.4.279 | 18 / 25 | |
| 0.4.278 | 18 / 25 | |
| 0.4.277 | 18 / 25 | |
| 0.4.276 | 18 / 25 | |
| 0.4.275 | 18 / 25 | |
| 0.4.274 | 18 / 25 | |
| 0.4.273 | 18 / 25 | |
| 0.4.272 | 18 / 25 | |
| 0.4.271 | 18 / 25 | |
| 0.4.270 | 18 / 25 | |
| 0.4.269 | 18 / 25 | |
| 0.4.268 | 18 / 25 | |
| 0.4.267 | 18 / 25 | |
| 0.4.266 | 18 / 25 | |
| 0.4.265 | 18 / 25 | |
| 0.4.264 | 18 / 25 | |
| 0.4.263 | 18 / 25 | |
| 0.4.262 | 18 / 25 | |
| 0.4.261 | 18 / 25 | |
| 0.4.260 | 18 / 25 | |
| 0.4.259 | 18 / 25 | |
| 0.4.258 | 18 / 25 | |
| 0.4.257 | 18 / 25 | |
| 0.4.256 | 18 / 25 | |
| 0.4.255 | 19 / 24 | |
| 0.4.254 | 19 / 24 | |
| 0.4.253 | 19 / 24 | |
| 0.4.252 | 19 / 24 | |
| 0.4.251 | 19 / 24 | |
| 0.4.250 | 19 / 24 | |
| 0.4.249 | 19 / 24 | |
| 0.4.248 | 19 / 24 | |
| 0.4.247 | 19 / 24 | |
| 0.4.246 | 19 / 24 | |
| 0.4.245 | 19 / 24 | |
| 0.4.244 | 19 / 24 | |
| 0.4.243 | 19 / 24 | |
| 0.4.242 | 19 / 24 | |
| 0.4.241 | 19 / 24 | |
| 0.4.240 | 19 / 24 | |
| 0.4.239 | 19 / 24 | |
| 0.4.238 | 19 / 24 | |
| 0.4.237 | 19 / 24 | |
| 0.4.236 | 19 / 24 | |
| 0.4.235 | 19 / 24 | |
| 0.4.234 | 19 / 24 | |
| 0.4.233 | 19 / 24 | |
| 0.4.232 | 19 / 24 | |
| 0.4.231 | 19 / 24 | |
| 0.4.230 | 19 / 24 | |
| 0.4.229 | 19 / 24 | |
| 0.4.228 | 19 / 24 | |
| 0.4.227 | 19 / 24 | |
| 0.4.226 | 19 / 24 | |
| 0.4.225 | 19 / 24 | |
| 0.4.224 | 19 / 24 | |
| 0.4.223 | 19 / 24 |
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.