@etrepum/lexical-builder-devtools-core
[EXPERIMENTAL] Lexical Builder Devtools
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 publisher with 293 approved packages; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@docusaurus/theme-mermaid | AI (phantom-deps): Declared in dependencies but used only in config files; stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 4 / 20 | |
| 0.3.0 | 4 / 20 | |
| 0.2.0 | 4 / 20 | |
| 0.1.0 | 4 / 20 | |
| 0.0.36 | 6 / 14 | |
| 0.0.35 | 6 / 14 | |
| 0.0.34 | 6 / 14 | |
| 0.0.33 | 6 / 14 | |
| 0.0.32 | 6 / 14 | |
| 0.0.31 | 6 / 14 | |
| 0.0.30 | 6 / 14 | |
| 0.0.29 | 6 / 14 | |
| 0.0.28 | 6 / 14 | |
| 0.0.27 | 6 / 14 | |
| 0.0.26 | 6 / 14 | |
| 0.0.25 | 6 / 12 | |
| 0.0.24 | 6 / 12 | |
| 0.0.23 | 6 / 12 | |
| 0.0.22 | 6 / 12 | |
| 0.0.21 | 6 / 12 | |
| 0.0.20 | 6 / 12 | |
| 0.0.19 | 6 / 12 | |
| 0.0.18 | 6 / 12 | |
| 0.0.17 | 6 / 12 |
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.