← Home

@knime/rich-text-editor

2
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

knime

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 2 of 203)

Version Deps Published
1.0.6 14 / 9
1.0.0 12 / 10

v1.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.