@rushstack/eslint-patch
Enhance ESLint with better support for large scale monorepos
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): This package's core purpose is patching ESLint module resolution; dynamic require() calls are fundamental to its design and not a security risk in this context. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft/RushStack package published by a long-standing trusted publisher; absence of Sigstore provenance is not a meaningful risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.16.1 | 0 / 9 | |
| 1.16.0 | 0 / 9 | |
| 1.15.0 | 0 / 9 | |
| 1.14.1 | 0 / 9 | |
| 1.14.0 | 0 / 9 | |
| 1.13.0 | 0 / 9 | |
| 1.12.0 | 0 / 8 | |
| 1.10.4 | 0 / 8 |
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.