@haklex/rich-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:thumbhash | AI (dependencies): thumbhash is a well-known, benign image placeholder library with no security concerns. | ai | |
| phantom-deps | phantom-dep:@base-ui/react | AI (phantom-deps): @base-ui/react is a declared peer dependency; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present for this package. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 6 / 20 | |
| 0.19.0 | 6 / 20 | |
| 0.18.0 | 6 / 20 | |
| 0.17.1 | 6 / 20 | |
| 0.16.1 | 6 / 20 | |
| 0.16.0 | 6 / 20 | |
| 0.15.9 | 6 / 20 | |
| 0.15.7 | 6 / 20 | |
| 0.15.6 | 6 / 20 | |
| 0.15.5 | 6 / 20 | |
| 0.15.4 | 6 / 20 | |
| 0.15.2 | 6 / 20 | |
| 0.15.1 | 6 / 20 | |
| 0.15.0 | 6 / 20 | |
| 0.14.1 | 7 / 20 | |
| 0.14.0 | 7 / 20 | |
| 0.13.0 | 7 / 20 | |
| 0.12.0 | 7 / 20 | |
| 0.11.0 | 7 / 20 | |
| 0.10.0 | 7 / 20 | |
| 0.9.3 | 7 / 20 | |
| 0.9.2 | 7 / 20 | |
| 0.9.1 | 6 / 20 | |
| 0.9.0 | 6 / 20 | |
| 0.8.0 | 6 / 20 | |
| 0.7.0 | 6 / 20 | |
| 0.6.2 | 6 / 20 | |
| 0.6.1 | 6 / 20 | |
| 0.6.0 | 6 / 20 | |
| 0.5.0 | 6 / 20 | |
| 0.4.1 | 6 / 20 | |
| 0.4.0 | 6 / 20 | |
| 0.3.2 | 6 / 20 | |
| 0.3.1 | 6 / 20 | |
| 0.2.0 | 6 / 20 | |
| 0.1.1 | 6 / 20 | |
| 0.0.110 | 6 / 20 | |
| 0.0.104 | 7 / 20 | |
| 0.0.98 | 7 / 20 | |
| 0.0.92 | 7 / 20 | |
| 0.0.89 | 7 / 20 | |
| 0.0.86 | 7 / 20 | |
| 0.0.81 | 7 / 20 | |
| 0.0.77 | 7 / 20 | |
| 0.0.70 | 6 / 21 | |
| 0.0.68 | 6 / 21 | |
| 0.0.65 | 6 / 21 | |
| 0.0.62 | 5 / 22 | |
| 0.0.56 | 5 / 22 | |
| 0.0.51 | 5 / 22 | |
| 0.0.50 | 5 / 22 |
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.