@crystaldesign/rtf-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:quill | AI (dependencies): quill is a well-known open-source rich text editor; expected dependency for an RTF editor package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 1568 versions; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal commercial component library; sparse metadata is consistent across 1566 versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this package's many versions; not a malware indicator here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 26.5.0 | 3 / 4 | |
| 26.4.8 | 3 / 4 | |
| 26.4.7 | 3 / 4 | |
| 26.4.5 | 3 / 4 | |
| 26.4.3 | 3 / 4 | |
| 26.4.1 | 3 / 4 | |
| 26.4.0 | 3 / 4 | |
| 26.3.2 | 3 / 4 | |
| 26.3.1 | 3 / 4 | |
| 26.3.0 | 3 / 4 | |
| 26.2.3 | 3 / 4 | |
| 26.1.2 | 3 / 4 | |
| 26.1.0 | 3 / 4 | |
| 25.14.4 | 3 / 4 | |
| 25.14.1 | 3 / 4 | |
| 25.14.0 | 3 / 4 | |
| 25.13.6 | 3 / 4 | |
| 25.13.5 | 3 / 4 | |
| 25.13.4 | 3 / 4 | |
| 25.13.3 | 3 / 4 | |
| 25.13.2 | 3 / 4 |
v26.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v26.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.