@lezer/css MIT 24 versions

@lezer/css

npm Repository Homepage

lezer-based CSS grammar

24

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

marijn

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@lezer/lr	AI (dependencies): @lezer/lr is a first-party dependency from the same @lezer ecosystem by the same author (Marijn Haverbeke); no security concern.	ai	2026/04/23
source-diff	obfuscated-file:dist/index.js	AI (source-diff): dist/index.js is a rollup-bundled build artifact from lezer-generator — readable, well-commented parser code. Long lines are normal for generated parser tables. Not obfuscation.	ai	2026/04/23
phantom-deps	phantom-dep:@lezer/common	AI (phantom-deps): @lezer/common is a shared types/utilities package within the same @lezer org scope; its use as a declared but indirectly imported dep is normal for this ecosystem.	ai	2026/04/21
bogus-package	bogus-package	AI (bogus-package): Inflated semver reflects pre-existing project history before npm publication. Published by established author Marijn Haverbeke. Not a spam/bogus package.	ai	2026/04/21
typosquat	typosquat.levenshtein:cors	AI (typosquat): @lezer/css is a scoped CSS grammar package with no relation to 'cors'; Levenshtein match is a clear false positive for this package.	ai	2026/04/21
typosquat	typosquat.levenshtein:qs	AI (typosquat): @lezer/css is a scoped CSS grammar package with no relation to 'qs'; Levenshtein match is a clear false positive for this package.	ai	2026/04/21

Versions (showing 24 of 24)

Version	Deps	Published
1.3.3	3 / 4	2026-03-23
1.3.2	3 / 4	2026-03-21
1.3.1	3 / 4	2026-02-16
1.3.0	3 / 4	2025-07-07
1.2.1	3 / 4	2025-05-15
1.2.0	3 / 4	2025-05-12
1.1.11	3 / 4	2025-03-24
1.1.10	3 / 4	2025-01-24
1.1.9	3 / 4	2024-09-10
1.1.8	3 / 4	2024-02-19
1.1.7	3 / 4	2024-01-08
1.1.6	3 / 4	2024-01-01
1.1.5	3 / 4	2023-12-28
1.1.4	2 / 4	2023-11-09
1.1.3	2 / 4	2023-07-03
1.1.2	2 / 4	2023-05-15
1.1.1	2 / 4	2022-12-02
1.1.0	2 / 4	2022-11-25
1.0.1	2 / 4	2022-10-10
1.0.0	2 / 4	2022-06-06
0.16.0	2 / 4	2022-04-20
0.15.2	1 / 4	2021-09-24
0.15.1	1 / 4	2021-08-31
0.15.0	1 / 4	2021-08-11

v1.3.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.

v1.3.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.

v1.3.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.

v1.2.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.

v1.2.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.

v1.1.11

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.

v1.1.10

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.

v1.1.9

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.

v1.1.8

2 findings

HIGH New obfuscated file: dist/index.js source-diff

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

LOW No provenance attestation provenance

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

v1.1.7

2 findings

HIGH New obfuscated file: dist/index.js source-diff

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

LOW No provenance attestation provenance

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

v1.1.6

2 findings

HIGH New obfuscated file: dist/index.js source-diff

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

LOW No provenance attestation provenance

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

v1.1.5

2 findings

HIGH New obfuscated file: dist/index.js source-diff

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

LOW No provenance attestation provenance

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

v1.1.4

2 findings

HIGH New obfuscated file: dist/index.js source-diff

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

LOW No provenance attestation provenance

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

v1.1.3

2 findings

HIGH New obfuscated file: dist/index.js source-diff

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

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.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.

v1.0.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.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.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.15.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.15.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.