@knime/rich-text-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 |
|---|---|---|---|---|
| license | uncommon-license:GPL 3 | AI (license): KNIME packages consistently use GPL-3 with additional permissions; stable for this org. | ai | |
| license | uncommon-license:Additional Permissions according to Sec. 7 SEE the file LICENSE | AI (license): Standard KNIME license addendum; stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): KNIME org packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:@knime/styles | AI (phantom-deps): Same-org monorepo dep; declared for transitive consumers, not directly imported in this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-character-count | AI (phantom-deps): Referenced in config/re-exported; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/starter-kit | AI (phantom-deps): Referenced in config/re-exported; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-underline | AI (phantom-deps): Referenced in config/re-exported; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 1.8.23 | 14 / 8 | |
| 1.8.22 | 14 / 8 | |
| 1.8.21 | 14 / 8 | |
| 1.8.20 | 14 / 8 | |
| 1.8.19 | 14 / 8 | |
| 1.8.18 | 14 / 8 | |
| 1.8.17 | 14 / 8 | |
| 1.8.16 | 14 / 8 | |
| 1.8.15 | 14 / 8 | |
| 1.8.14 | 14 / 8 | |
| 1.8.13 | 14 / 8 | |
| 1.8.12 | 14 / 8 | |
| 1.8.11 | 14 / 8 | |
| 1.8.10 | 14 / 8 | |
| 1.8.9 | 14 / 8 | |
| 1.8.8 | 14 / 8 | |
| 1.8.7 | 14 / 8 | |
| 1.8.6 | 14 / 8 | |
| 1.8.5 | 14 / 8 | |
| 1.8.4 | 14 / 8 | |
| 1.8.3 | 14 / 8 | |
| 1.8.2 | 14 / 8 | |
| 1.8.1 | 14 / 8 | |
| 1.8.0 | 14 / 8 | |
| 1.7.42 | 14 / 8 | |
| 1.7.41 | 14 / 8 | |
| 1.7.40 | 14 / 8 | |
| 1.7.39 | 14 / 8 | |
| 1.7.38 | 14 / 8 | |
| 1.7.37 | 14 / 8 | |
| 1.7.36 | 14 / 8 | |
| 1.7.35 | 14 / 8 | |
| 1.7.34 | 14 / 8 | |
| 1.7.33 | 14 / 8 | |
| 1.7.32 | 14 / 8 | |
| 1.7.31 | 14 / 8 | |
| 1.7.30 | 14 / 8 | |
| 1.7.29 | 14 / 8 | |
| 1.7.28 | 14 / 8 | |
| 1.7.27 | 14 / 8 | |
| 1.7.26 | 14 / 8 | |
| 1.7.25 | 14 / 8 | |
| 1.7.24 | 14 / 8 | |
| 1.7.23 | 14 / 8 | |
| 1.7.22 | 14 / 8 | |
| 1.7.21 | 14 / 8 | |
| 1.7.20 | 14 / 8 | |
| 1.7.19 | 14 / 8 | |
| 1.7.18 | 14 / 8 | |
| 1.7.17 | 14 / 8 | |
| 1.7.16 | 14 / 8 |
v1.8.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.