@lezer/php
Lezer-based PHP 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @lezer/php is a scoped PHP grammar package in the Lezer ecosystem, not a typosquat of 'pg'. Levenshtein match is purely coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @lezer/php is a scoped PHP grammar package in the Lezer ecosystem, not a typosquat of 'yup'. Levenshtein match is purely coincidental. | ai | |
| phantom-deps | phantom-dep:@lezer/common | AI (phantom-deps): @lezer/common is a legitimate peer/transitive dependency in the Lezer ecosystem; phantom detection is a false positive for grammar packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals are cosmetic quality issues. Starting at 1.0.5 reflects prior versioning history of the grammar. Published by the Lezer ecosystem author. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 3 / 4 | |
| 1.0.4 | 3 / 4 | |
| 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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.