@chevrotain/gast
Grammar AST structure for Chevrotain Parsers
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @chevrotain/gast is a well-established parser toolkit component, not a typosquat of jest. Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @chevrotain/gast is a well-established parser toolkit component, not a typosquat of got. Levenshtein match is a false positive. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation — this is a legitimate CI/CD migration for the official Chevrotain monorepo, not a compromise. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 12.0.0 | 1 / 0 | |
| 11.2.0 | 2 / 1 | |
| 11.1.2 | 2 / 1 | |
| 11.1.1 | 2 / 1 | |
| 11.1.0 | 2 / 1 | |
| 11.0.3 | 2 / 1 | |
| 11.0.2 | 2 / 1 | |
| 11.0.1 | 2 / 1 | |
| 11.0.0 | 2 / 1 |
v12.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.