@procore/text-editor
Rich text editor component based on CKEditor 5
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in a codemod test file (execFileSync) — standard test tooling, not a runtime risk. | ai | |
| phantom-deps | phantom-dep:@procore/core-icons | AI (phantom-deps): Same-org dep; likely used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@procore/core-i18n-js | AI (phantom-deps): Same-org dep; likely used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@react-aria/focus | AI (phantom-deps): Referenced in config files; phantom-dep heuristic misfires on config-only usage. | ai | |
| phantom-deps | phantom-dep:@react-aria/utils | AI (phantom-deps): Referenced in config files; phantom-dep heuristic misfires on config-only usage. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 6 / 55 | |
| 0.4.1 | 6 / 55 | |
| 0.4.0 | 6 / 55 | |
| 0.3.2 | 6 / 54 | |
| 0.3.1 | 6 / 54 | |
| 0.3.0 | 6 / 54 | |
| 0.2.1 | 6 / 54 | |
| 0.2.0 | 6 / 54 | |
| 0.1.0 | 6 / 54 | |
| 0.0.3 | 6 / 55 | |
| 0.0.2 | 6 / 59 | |
| 0.0.1 | 6 / 59 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
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.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.