@lexical/eslint-plugin
Lexical specific linting rules for ESLint
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Facebook/Lexical package; provenance not historically present, low risk. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.44.0 | 0 / 2 | |
| 0.43.0 | 0 / 2 | |
| 0.42.0 | 0 / 2 | |
| 0.41.0 | 0 / 2 | |
| 0.40.0 | 0 / 2 | |
| 0.39.0 | 0 / 1 | |
| 0.38.2 | 0 / 1 | |
| 0.38.1 | 0 / 1 | |
| 0.38.0 | 0 / 1 | |
| 0.37.0 | 0 / 1 | |
| 0.36.2 | 0 / 1 | |
| 0.36.1 | 0 / 1 | |
| 0.36.0 | 0 / 1 | |
| 0.35.0 | 0 / 1 | |
| 0.34.0 | 0 / 1 | |
| 0.33.1 | 0 / 1 | |
| 0.33.0 | 0 / 1 | |
| 0.32.1 | 0 / 1 | |
| 0.32.0 | 0 / 1 | |
| 0.31.2 | 0 / 1 | |
| 0.31.1 | 0 / 1 | |
| 0.31.0 | 0 / 1 | |
| 0.30.0 | 0 / 1 | |
| 0.29.0 | 0 / 1 | |
| 0.28.0 | 0 / 1 | |
| 0.27.2 | 0 / 1 | |
| 0.27.1 | 0 / 1 | |
| 0.27.0 | 0 / 1 | |
| 0.26.0 | 0 / 1 | |
| 0.25.0 | 0 / 1 | |
| 0.24.0 | 0 / 1 | |
| 0.23.1 | 0 / 1 | |
| 0.23.0 | 0 / 1 | |
| 0.22.0 | 0 / 1 | |
| 0.21.0 | 0 / 1 | |
| 0.20.2 | 0 / 1 | |
| 0.20.1 | 0 / 1 | |
| 0.20.0 | 0 / 1 | |
| 0.19.0 | 0 / 1 | |
| 0.18.0 | 0 / 1 | |
| 0.17.1 | 0 / 1 | |
| 0.17.0 | 0 / 1 | |
| 0.16.1 | 0 / 1 | |
| 0.16.0 | 0 / 1 | |
| 0.15.0 | 0 / 1 |
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.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.
v0.15.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.