@lezer/json
lezer-based JSON grammar
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jsdom | AI (typosquat): Unrelated package; edit-distance false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Unrelated package; edit-distance false positive. | ai | |
| phantom-deps | phantom-dep:@lezer/common | AI (phantom-deps): Same-org monorepo dependency, not phantom. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 3 / 4 | |
| 1.0.2 | 3 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.16.0 | 2 / 4 | |
| 0.15.0 | 1 / 4 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.