@etrepum/lexical-builder-markdown MIT 16 versions

@etrepum/lexical-builder-markdown

npm Repository Homepage

[EXPERIMENTAL] Lexical Builder @etrepum/lexical-builder-markdown

16

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

etrepum

Keywords

lexicallexical-builderplug-inextensionmarkdown

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@etrepum/lexical-builder-list	AI (dependencies): Same-org monorepo sibling package, not third-party.	ai	2026/07/10
publish-pattern	new-deps-added	AI (publish-pattern): Sibling package add, consistent with monorepo split pattern.	ai	2026/07/10
phantom-deps	phantom-dep:@etrepum/lexical-builder-list	AI (phantom-deps): Sibling monorepo package; likely re-exported rather than directly imported in this markdown plugin.	ai	2026/05/09

Versions (showing 16 of 16)

Version	Deps	Published
0.4.0	0 / 19	2026-03-31
0.3.0	0 / 19	2026-03-28
0.2.0	0 / 19	2026-03-19
0.1.0	0 / 19	2026-03-17
0.0.36	2 / 12	2025-07-14
0.0.35	2 / 12	2024-08-12
0.0.34	2 / 12	2024-08-12
0.0.33	2 / 12	2024-08-12
0.0.32	2 / 12	2024-08-10
0.0.31	2 / 12	2024-07-24
0.0.30	2 / 12	2024-07-16
0.0.29	2 / 12	2024-07-09
0.0.28	2 / 12	2024-07-09
0.0.27	2 / 12	2024-07-01
0.0.26	1 / 12	2024-06-26
0.0.25	1 / 10	2024-06-24

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.34

1 finding

LOW No provenance attestation provenance

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

v0.0.33

1 finding

LOW No provenance attestation provenance

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

v0.0.32

1 finding

LOW No provenance attestation provenance

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

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

1 finding

LOW No provenance attestation provenance

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

v0.0.29

1 finding

LOW No provenance attestation provenance

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

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

1 finding

LOW No provenance attestation provenance

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

v0.0.26

1 finding

LOW No provenance attestation provenance

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

v0.0.25

1 finding

LOW No provenance attestation provenance

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