@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, so a manually published version cannot be tied back to a reviewed commit.
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-RG3FN6WF.js | AI (source-diff): esbuild-minified client bundle; build output not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-OHQPCDNR.js | AI (source-diff): esbuild-minified client bundle; benign build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-NNKG7K3O.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; expected build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-IUDF2DGI.js | AI (source-diff): esbuild-minified client bundle; build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-53MM7FV7.js | AI (source-diff): esbuild-minified client bundle; expected build output for this package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-DTQOXLGX.js | AI (source-diff): esbuild-bundled client component, not obfuscation; expected for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-ZQTPXWY3.js | AI (source-diff): esbuild-minified client bundle; standard build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-VBZQOYLK.js | AI (source-diff): esbuild-minified client bundle; standard minified dist output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-TYBPYPLA.js | AI (source-diff): esbuild-minified client bundle with readable imports; build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-NUQPQ2MC.js | AI (source-diff): esbuild-minified build output, hashed filenames rotate per release; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-F5XP4HL4.js | AI (source-diff): esbuild-minified build output; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-JP7H7AZE.js | AI (source-diff): esbuild-minified React client bundle; benign build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-C3BBYNYR.js | AI (source-diff): esbuild-minified client bundle; build output not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-7ROJ5JAM.js | AI (source-diff): esbuild-bundled client chunk; standard minified build output for this package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-OQJ5KXCS.js | AI (source-diff): esbuild-bundled client chunk with readable imports; minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-US3A77DK.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; stable build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-7XFZE2MU.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; regenerated per release. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-QUXIGJRC.js | AI (source-diff): esbuild-bundled client field component, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-LOLYH42M.js | AI (source-diff): esbuild-minified dist output, not obfuscation; expected for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-IS3XMKMO.js | AI (source-diff): esbuild-bundled client component; minified build output, not obfuscation. Stable for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-OIMYWB22.js | AI (source-diff): esbuild/swc bundle output; minified not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-HJGV32KA.js | AI (source-diff): esbuild-bundled client output, readable ESM imports; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-XIHC3W6W.js | AI (source-diff): Minified esbuild output, readable imports, no obfuscation signature; stable for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-5IW2M4GH.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; expected build output for this package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-FLAQN6LU.js | AI (source-diff): esbuild-minified React client bundle; readable imports, benign. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-Y3OSWJM5.js | AI (source-diff): esbuild-minified client bundle with legible imports; standard build output for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large monorepo dist output; expected for this UI-heavy package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-2A2VQXKP.js | AI (source-diff): Bundled/minified esbuild output, not obfuscation; regenerated per build. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-YQ22OGQW.js | AI (source-diff): Bundled/minified esbuild output, not obfuscation; regenerated per build. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-43GHEACW.js | AI (source-diff): esbuild-minified ESM build output, not obfuscation; stable for this bundled package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-5YLBQB5B.js | AI (source-diff): esbuild-minified ESM build output, not obfuscation; stable for this bundled package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-X3CJV3SY.js | AI (source-diff): esbuild-bundled client output, not obfuscation; content is minified React/lexical. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-NNWFQETL.js | AI (source-diff): esbuild-bundled client chunk; minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-P5K7Z5NW.js | AI (source-diff): esbuild-bundled client chunk with readable imports; minified build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-JOPOYQQ5.js | AI (source-diff): esbuild-minified client bundle, readable import graph. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-VJVZFYZJ.js | AI (source-diff): esbuild-minified client bundle per documented build flow, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-G3GIPW2U.js | AI (source-diff): esbuild-minified dist output, not obfuscation; regenerated per build. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-FMNFWV4P.js | AI (source-diff): esbuild-minified client bundle; readable ESM imports, no payload. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-NSAU5Y76.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; expected build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-KHGUSLMB.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; expected build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-D6PKVJ2K.js | AI (source-diff): esbuild-minified client bundle with clean imports; build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-4JYUMYYH.js | AI (source-diff): esbuild-minified client bundle; build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/exports/client/component-UYO2QYQP.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; canonical build output for this package. | ai | |
| phantom-deps | phantom-dep:dequal | AI (phantom-deps): Used transitively/via config; stable FP for this package. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-MAUKSOAP.js | AI (source-diff): esbuild-minified client bundle, not obfuscation; canonical build output. | ai | |
| source-diff | obfuscated-file:dist/exports/client/Field-J6MIUIWP.js | AI (source-diff): esbuild bundle output with readable ESM imports; minified not obfuscated, stable for this build pipeline. | ai | |
| 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 | |
| provenance | no-provenance | AI (provenance): Established official PayloadCMS package; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@payloadcms/translations | AI (dependencies): First-party PayloadCMS package, co-versioned with this package. | ai | |
| dependencies | unvetted-dep:@payloadcms/ui | AI (dependencies): First-party PayloadCMS package, co-versioned with this package. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 3.86.0 | 27 / 18 | |
| 3.85.2 | 27 / 18 | |
| 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 | |
| 3.80.0 | 28 / 18 | |
| 3.79.1 | 28 / 18 | |
| 3.79.0 | 28 / 18 | |
| 3.78.0 | 28 / 18 | |
| 3.77.0 | 28 / 18 | |
| 3.76.1 | 28 / 18 | |
| 3.76.0 | 28 / 18 | |
| 3.75.0 | 28 / 18 | |
| 3.74.0 | 28 / 18 | |
| 3.73.0 | 28 / 18 | |
| 3.72.0 | 28 / 18 | |
| 3.71.1 | 28 / 18 | |
| 3.71.0 | 28 / 18 | |
| 3.70.0 | 28 / 18 | |
| 3.69.0 | 28 / 18 | |
| 3.68.5 | 28 / 18 | |
| 3.68.4 | 28 / 18 | |
| 3.68.3 | 28 / 18 | |
| 3.68.2 | 28 / 18 | |
| 3.68.1 | 28 / 18 | |
| 3.68.0 | 28 / 18 | |
| 3.67.0 | 28 / 18 | |
| 3.66.0 | 28 / 18 | |
| 3.65.0 | 28 / 18 | |
| 3.64.0 | 28 / 18 | |
| 3.63.0 | 28 / 18 | |
| 3.62.1 | 28 / 18 | |
| 3.62.0 | 28 / 18 | |
| 3.32.0 | 26 / 19 | |
| 3.31.0 | 26 / 19 | |
| 3.30.0 | 26 / 19 | |
| 3.29.0 | 26 / 19 | |
| 3.28.1 | 26 / 19 | |
| 3.28.0 | 26 / 19 | |
| 3.27.0 | 25 / 19 | |
| 3.26.0 | 25 / 19 | |
| 3.25.0 | 25 / 19 | |
| 3.24.0 | 25 / 19 | |
| 3.23.0 | 24 / 19 | |
| 3.22.0 | 24 / 19 | |
| 3.21.0 | 24 / 19 | |
| 3.20.0 | 24 / 19 | |
| 3.19.0 | 24 / 19 | |
| 3.18.0 | 24 / 19 | |
| 3.17.1 | 24 / 19 | |
| 3.17.0 | 24 / 19 | |
| 3.16.0 | 24 / 19 | |
| 3.15.1 | 24 / 19 | |
| 3.15.0 | 24 / 19 | |
| 3.14.0 | 24 / 19 | |
| 3.13.0 | 24 / 19 | |
| 3.12.0 | 24 / 19 | |
| 3.11.0 | 23 / 19 | |
| 3.10.0 | 23 / 19 | |
| 3.9.0 | 23 / 19 | |
| 3.8.0 | 23 / 19 | |
| 3.7.0 | 23 / 19 | |
| 3.6.0 | 23 / 19 | |
| 3.5.0 | 22 / 19 | |
| 3.4.0 | 22 / 19 | |
| 3.3.0 | 22 / 19 | |
| 3.2.2 | 22 / 19 | |
| 3.2.1 | 22 / 19 | |
| 3.2.0 | 22 / 19 | |
| 3.1.1 | 22 / 19 | |
| 3.1.0 | 22 / 19 | |
| 3.0.2 | 22 / 19 | |
| 3.0.1 | 23 / 19 | |
| 3.0.0 | 23 / 19 |
v3.86.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.85.2
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.80.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.79.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.79.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.78.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.77.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.76.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.76.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.75.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.74.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.73.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.72.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.71.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.71.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.70.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.69.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.68.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.68.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.68.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.68.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.68.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.68.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.67.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.66.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.65.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.64.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.63.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.62.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.62.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.32.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.31.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.30.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.29.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.28.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.28.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.27.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.26.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.25.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.24.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.23.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.22.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.21.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.20.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.19.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.18.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.17.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.17.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.16.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.15.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.15.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.14.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.13.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.12.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.11.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.10.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.9.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.8.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.7.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.6.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.1.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.0.2
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.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.