@lexical/code-shiki MIT 11 versions

@lexical/code-shiki

npm Repository Homepage

This package contains the code highlighter for Lexical using shikijs engine

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

fantactukazurfyxacywatsonipavlov001trueadmetrepum

Keywords

lexicaleditorrich-textcode

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:shiki	AI (phantom-deps): Shiki is a declared dependency referenced in config; stable for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@shikijs/core	AI (phantom-deps): Declared dependency referenced in config; stable for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@shikijs/langs	AI (phantom-deps): Declared dependency referenced in config; stable for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@shikijs/themes	AI (phantom-deps): Declared dependency referenced in config; stable for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@shikijs/engine-javascript	AI (phantom-deps): Declared dependency referenced in config; stable for this package.	ai	2026/04/29

Versions (showing 11 of 11)

Version	Deps	Published
0.44.0	8 / 1	2026-04-27
0.39.0	8 / 1	2025-12-10
0.38.2	8 / 1	2025-10-31
0.38.1	8 / 1	2025-10-27
0.38.0	8 / 1	2025-10-27
0.37.0	8 / 1	2025-10-11
0.36.2	8 / 1	2025-10-01
0.36.1	8 / 1	2025-09-25
0.36.0	8 / 1	2025-09-25
0.35.0	8 / 1	2025-09-05
0.34.0	8 / 1	2025-08-08

v0.39.0

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.

v0.38.2

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.

v0.38.1

1 finding

LOW No provenance attestation provenance

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

v0.38.0

1 finding

LOW No provenance attestation provenance

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

v0.37.0

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.

v0.36.2

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.

v0.36.1

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.

v0.36.0

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.

v0.35.0

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.

v0.34.0

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.