← Home

lexical

npm Repository Homepage
51
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

fantactukatrueadmzurfyxacywatsonipavlov001etrepum

Keywords

reactlexicaleditorcontenteditablerich-text

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): CLI tool's documented exec usage, not malicious; stable across versions. ai
source-diff obfuscated-file:Lexical.prod.mjs AI (source-diff): Standard minified production bundle shipped every release; benign for this package. ai
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI/CD with SLSA attestation; expected for facebook/lexical. ai
source-diff obfuscated-file:dist/Lexical.dev.mjs AI (source-diff): Dev bundle with long lines but fully readable code; false positive. ai
source-diff large-new-source-files AI (source-diff): Lexical ships source + dist bundles; large file count is normal for this package. ai
source-diff obfuscated-file:dist/Lexical.prod.js AI (source-diff): Standard minified production bundle for this package; dev counterpart is readable. ai
source-diff obfuscated-file:dist/Lexical.prod.mjs AI (source-diff): Standard minified production ESM bundle; dev counterpart is readable. ai
provenance no-provenance AI (provenance): Lexical is a well-established Facebook/Meta package with 597 versions and strong ecosystem trust. Lack of Sigstore attestation is a hygiene issue, not a security risk for this package. ai

Versions (showing 51 of 137)

View all versions
Version Deps Published
0.48.0 1 / 0
0.47.0 1 / 0
0.46.0 1 / 0
0.45.0 1 / 0
0.44.0 0 / 0
0.43.0 0 / 0
0.42.0 0 / 0
0.41.0 0 / 0
0.40.0 0 / 0
0.39.0 0 / 0
0.38.2 0 / 0
0.38.1 0 / 0
0.38.0 0 / 0
0.37.0 0 / 0
0.36.2 0 / 0
0.36.1 0 / 0
0.36.0 0 / 0
0.35.0 0 / 0
0.34.0 0 / 0
0.33.1 0 / 0
0.33.0 0 / 0
0.32.1 0 / 0
0.32.0 0 / 0
0.31.2 0 / 0
0.31.1 0 / 0
0.31.0 0 / 0
0.30.0 0 / 0
0.29.0 0 / 0
0.28.0 0 / 0
0.27.2 0 / 0
0.27.1 0 / 0
0.27.0 0 / 0
0.26.0 0 / 0
0.25.0 0 / 0
0.24.0 0 / 0
0.23.1 0 / 0
0.23.0 0 / 0
0.22.0 0 / 0
0.21.0 0 / 0
0.20.2 0 / 0
0.20.1 0 / 0
0.20.0 0 / 0
0.19.0 0 / 0
0.18.0 0 / 0
0.17.1 0 / 0
0.17.0 0 / 0
0.16.1 0 / 0
0.16.0 0 / 0
0.15.0 0 / 0
0.14.5 0 / 0
0.14.4 0 / 0

v0.48.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.47.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.30.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.29.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.28.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.27.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: acywatson → zurfyx (on 2025-02-21, known maintainer) provenance

This version was published by a different npm account (zurfyx) than the most recent previously approved version (acywatson) on 2025-02-21, but zurfyx is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.24.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: acywatson → zurfyx (on 2025-02-07, known maintainer) provenance

This version was published by a different npm account (zurfyx) than the most recent previously approved version (acywatson) on 2025-02-07, but zurfyx is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.23.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.15.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.14.5

2 findings
HIGH New obfuscated file: Lexical.prod.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.4

2 findings
HIGH New obfuscated file: Lexical.prod.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.