@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 — 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: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 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.7.13 | 18 / 25 | |
| 0.7.12 | 18 / 25 | |
| 0.7.7 | 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 |
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.278
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.277
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.276
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.273
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.269
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.267
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.