@payloadcms/richtext-lexical
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/exports/client/Field-KR4W3EZZ.js | AI (source-diff): Bundled/minified client output from esbuild pipeline; standard for this package's build process. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): @types/uuid is explicitly listed as a runtime dependency in package.json; phantom-dep is a false positive for this package. | ai | |
| dependencies | unvetted-dep:@payloadcms/ui | AI (dependencies): First-party PayloadCMS package, co-versioned with this package. | ai | |
| dependencies | unvetted-dep:@payloadcms/translations | AI (dependencies): First-party PayloadCMS package, co-versioned with this package. | ai | |
| provenance | no-provenance | AI (provenance): Established official PayloadCMS package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.85.1 | 27 / 18 | |
| 3.85.0 | 27 / 18 | |
| 3.84.1 | 27 / 18 | |
| 3.84.0 | 27 / 18 | |
| 3.83.0 | 27 / 18 | |
| 3.82.1 | 28 / 18 | |
| 3.82.0 | 28 / 18 | |
| 3.81.0 | 28 / 18 |
v3.85.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.83.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.82.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.82.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.81.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.