← Home

@lezer/xml

npm Repository Homepage

lezer-based XML grammar

10
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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@lezer/lr AI (dependencies): @lezer/lr is the core Lezer LR parser runtime from the same author/org as this package; it is a fundamental and expected dependency. ai
source-diff obfuscated-file:dist/index.js AI (source-diff): dist/index.js is a rollup-bundled build artifact from lezer-generator; long lines are parser tables, not obfuscation. Standard for all @lezer/* packages. ai
bogus-package bogus-package AI (bogus-package): Legitimate lezer ecosystem package by Marijn Haverbeke; inflated semver reflects migration history, not spam. Short README and no keywords are quality issues only. ai
phantom-deps phantom-dep:@lezer/common AI (phantom-deps): @lezer/common is a legitimate peer/type dependency in the lezer ecosystem; same org scope as this package. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.6 3 / 4
1.0.5 3 / 4
1.0.4 3 / 4
1.0.3 2 / 4
1.0.2 2 / 4
1.0.1 2 / 4
1.0.0 2 / 4
0.16.0 2 / 4
0.15.1 1 / 4
0.15.0 1 / 4

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

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