@blocklet/editor
Rich editor powered by lexical.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/ext/PasteMarkdownPlugin/index.spec.js | AI (source-diff): Vitest spec with a long HTML fixture string, not obfuscated/minified code. | ai | |
| provenance | missing-githead | AI (provenance): Trusted high-volume publisher; likely publish-env variance, not tampering. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @iconify/react is a well-known, established icon library. | ai | |
| phantom-deps | phantom-dep:@lexical/file | AI (phantom-deps): Lexical ecosystem dep; may be used indirectly via config/plugins, stable false positive. | ai | |
| phantom-deps | phantom-dep:@blocklet/code-editor | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lexical/clipboard | AI (phantom-deps): Lexical ecosystem dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Peer/transitive usage pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@blocklet/pages-kit-inner-components | AI (phantom-deps): Same-org package; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lexical/yjs | AI (phantom-deps): Lexical ecosystem dep; may be used indirectly via config/plugins, stable false positive. | ai |
Versions (showing 100 of 664)
| Version | Deps | Published |
|---|---|---|
| 2.5.18 | 49 / 24 | |
| 2.5.17 | 49 / 24 | |
| 2.5.16 | 49 / 24 | |
| 2.5.15 | 49 / 24 | |
| 2.5.14 | 49 / 24 | |
| 2.5.13 | 49 / 24 | |
| 2.5.12 | 49 / 24 | |
| 2.5.11 | 49 / 24 | |
| 2.5.10 | 49 / 24 | |
| 2.5.9 | 49 / 24 | |
| 2.5.8 | 49 / 24 | |
| 2.5.7 | 49 / 24 | |
| 2.5.6 | 49 / 24 | |
| 2.5.5 | 49 / 24 | |
| 2.5.4 | 49 / 24 | |
| 2.5.3 | 49 / 24 | |
| 2.5.2 | 49 / 24 | |
| 2.5.1 | 49 / 24 | |
| 2.5.0 | 49 / 24 | |
| 2.4.126 | 49 / 24 | |
| 2.4.125 | 49 / 24 | |
| 2.4.124 | 49 / 24 | |
| 2.4.123 | 49 / 24 | |
| 2.4.122 | 49 / 24 | |
| 2.4.121 | 49 / 24 | |
| 2.4.120 | 49 / 24 | |
| 2.4.119 | 49 / 24 | |
| 2.4.118 | 49 / 24 | |
| 2.4.117 | 49 / 24 | |
| 2.4.116 | 49 / 24 | |
| 2.4.115 | 49 / 24 | |
| 2.4.114 | 49 / 24 | |
| 2.4.112 | 49 / 24 | |
| 2.4.111 | 49 / 24 | |
| 2.4.110 | 49 / 24 | |
| 2.4.109 | 49 / 24 | |
| 2.4.108 | 49 / 24 | |
| 2.4.107 | 49 / 24 | |
| 2.4.106 | 49 / 24 | |
| 2.4.105 | 49 / 24 | |
| 2.4.104 | 49 / 24 | |
| 2.4.103 | 49 / 24 | |
| 2.4.102 | 49 / 24 | |
| 2.4.93 | 49 / 24 | |
| 2.4.74 | 47 / 24 | |
| 2.4.73 | 47 / 24 | |
| 2.4.72 | 47 / 24 | |
| 2.4.71 | 47 / 24 | |
| 2.4.70 | 47 / 24 | |
| 2.4.69 | 47 / 24 | |
| 2.4.68 | 47 / 24 | |
| 2.4.67 | 47 / 24 | |
| 2.4.66 | 47 / 24 | |
| 2.4.65 | 47 / 24 | |
| 2.4.64 | 47 / 24 | |
| 2.4.63 | 47 / 24 | |
| 2.4.62 | 47 / 24 | |
| 2.4.61 | 47 / 24 | |
| 2.4.60 | 47 / 24 | |
| 2.4.59 | 47 / 24 | |
| 2.4.58 | 47 / 24 | |
| 2.4.57 | 46 / 24 | |
| 2.4.56 | 46 / 24 | |
| 2.4.55 | 46 / 24 | |
| 2.4.54 | 46 / 24 | |
| 2.4.53 | 46 / 24 | |
| 2.4.52 | 46 / 24 | |
| 2.4.51 | 46 / 24 | |
| 2.4.50 | 46 / 24 | |
| 2.4.49 | 46 / 24 | |
| 2.4.48 | 46 / 24 | |
| 2.4.47 | 46 / 24 | |
| 2.4.46 | 46 / 24 | |
| 2.4.45 | 46 / 24 | |
| 2.4.44 | 46 / 24 | |
| 2.4.43 | 46 / 24 | |
| 2.4.42 | 46 / 24 | |
| 2.4.41 | 46 / 24 | |
| 2.4.40 | 46 / 24 | |
| 2.4.39 | 46 / 24 | |
| 2.4.38 | 46 / 24 | |
| 2.4.37 | 46 / 24 | |
| 2.4.36 | 46 / 24 | |
| 2.4.35 | 46 / 24 | |
| 2.4.34 | 46 / 24 | |
| 2.4.33 | 46 / 24 | |
| 2.4.32 | 46 / 24 | |
| 2.4.31 | 46 / 24 | |
| 2.4.30 | 46 / 24 | |
| 2.4.29 | 46 / 24 | |
| 2.4.28 | 46 / 24 | |
| 2.4.27 | 46 / 24 | |
| 2.4.26 | 46 / 24 | |
| 2.4.25 | 46 / 24 | |
| 2.4.24 | 46 / 24 | |
| 2.4.23 | 46 / 24 | |
| 2.4.22 | 46 / 24 | |
| 2.4.21 | 46 / 24 | |
| 2.4.20 | 46 / 24 | |
| 2.4.19 | 46 / 24 |
v2.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.41
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.40
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.39
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.38
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.37
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.36
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.35
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.34
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.33
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.32
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.31
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.30
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.29
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.28
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.27
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.26
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.25
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.24
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.23
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.22
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.21
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.20
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.19
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wangshijun.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.