@reacteditor/core
The open-source visual editor for React
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): @emotion/react is a peer dep of @chakra-ui/react; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:deep-diff | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires on config/test references, not a real concern. | ai | |
| phantom-deps | phantom-dep:happy-dom | AI (phantom-deps): Test environment dep; phantom-dep heuristic false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped React editor package; Levenshtein match to 'cors' is purely coincidental given the package's purpose and dependency set. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/helpers | AI (phantom-deps): dnd-kit helper dep; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:react-hotkeys-hook | AI (phantom-deps): Runtime dep for hotkeys; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@tiptap/pm | AI (phantom-deps): Tiptap peer dep; phantom-dep heuristic false positive for this editor package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.0.34 | 39 / 22 | |
| 0.0.33 | 39 / 22 | |
| 0.0.31 | 39 / 22 | |
| 0.0.30 | 39 / 22 | |
| 0.0.29 | 39 / 22 | |
| 0.0.28 | 39 / 21 | |
| 0.0.27 | 39 / 21 | |
| 0.0.26 | 40 / 21 | |
| 0.0.25 | 40 / 21 | |
| 0.0.24 | 40 / 21 | |
| 0.0.23 | 40 / 21 | |
| 0.0.22 | 40 / 22 | |
| 0.0.21 | 40 / 22 | |
| 0.0.20 | 40 / 22 | |
| 0.0.19 | 40 / 22 | |
| 0.0.18 | 40 / 22 | |
| 0.0.17 | 40 / 22 | |
| 0.0.16 | 40 / 22 | |
| 0.0.15 | 41 / 22 | |
| 0.0.14 | 40 / 22 | |
| 0.0.13 | 40 / 22 | |
| 0.0.12 | 40 / 22 | |
| 0.0.11 | 40 / 22 | |
| 0.0.10 | 40 / 22 | |
| 0.0.9 | 40 / 22 | |
| 0.0.8 | 40 / 22 | |
| 0.0.7 | 40 / 22 | |
| 0.0.6 | 40 / 22 | |
| 0.0.5 | 39 / 22 | |
| 0.0.4 | 39 / 22 | |
| 0.0.3 | 34 / 22 | |
| 0.0.2 | 34 / 22 |
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.