@renovatebot/good-enough-parser
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is a cosmetic metadata gap, not a supply-chain risk for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): devops-mend is the Mend/WhiteSource org that maintains Renovate; addition is expected for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Renovatebot org migrated publishing to GitHub Actions CI/CD; SLSA provenance attestation confirms supply chain integrity. | ai | |
| dependencies | unvetted-dep:moo | AI (dependencies): moo is a well-known lexer library pinned to a specific version; stable dependency for this parser package. | ai | |
| phantom-deps | phantom-dep:@types/moo | AI (phantom-deps): @types/moo is a type-only package used at compile time; not directly imported at runtime by convention. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 4 / 26 | |
| 2.0.0 | 4 / 26 | |
| 1.2.0 | 4 / 25 | |
| 1.1.24 | 4 / 25 |
v2.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. 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.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.