@rnx-kit/eslint-plugin
A set of ESLint rules for React developers
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Explicitly listed in depcheck.ignoreMatches; used via config, not import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Explicitly listed in depcheck.ignoreMatches; used via config, not import. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): Explicitly listed in depcheck.ignoreMatches; used via config, not import. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known Microsoft OSS maintainer handoff within trusted org repo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer rotation, no behavioral change in package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): Explicitly listed in depcheck.ignoreMatches; used via config, not import. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft rnx-kit uses a bot publisher; lack of Sigstore provenance is acceptable given the established package history and clear Microsoft authorship. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in ESLint config files is standard practice for this plugin; it resolves config paths conditionally, not from user-controlled input. Stable false positive for this package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.9.9 | 5 / 10 | |
| 0.9.8 | 5 / 10 | |
| 0.9.7 | 5 / 10 | |
| 0.9.6 | 5 / 9 | |
| 0.9.5 | 5 / 9 | |
| 0.9.4 | 5 / 9 | |
| 0.9.3 | 5 / 9 | |
| 0.9.2 | 5 / 9 | |
| 0.9.1 | 5 / 9 | |
| 0.9.0 | 5 / 9 | |
| 0.8.6 | 5 / 14 | |
| 0.8.5 | 5 / 14 | |
| 0.8.4 | 5 / 15 | |
| 0.8.3 | 6 / 16 | |
| 0.8.2 | 6 / 18 | |
| 0.8.1 | 7 / 18 | |
| 0.8.0 | 7 / 18 | |
| 0.7.2 | 7 / 18 | |
| 0.7.1 | 7 / 18 | |
| 0.7.0 | 8 / 17 | |
| 0.6.0 | 8 / 16 | |
| 0.5.3 | 6 / 12 | |
| 0.5.2 | 5 / 8 | |
| 0.5.1 | 5 / 8 | |
| 0.5.0 | 5 / 8 | |
| 0.4.2 | 5 / 7 | |
| 0.4.1 | 5 / 4 | |
| 0.4.0 | 5 / 4 | |
| 0.3.0 | 5 / 4 | |
| 0.2.13 | 5 / 4 | |
| 0.2.12 | 5 / 4 | |
| 0.2.11 | 5 / 3 | |
| 0.2.10 | 4 / 3 | |
| 0.2.9 | 5 / 3 | |
| 0.2.8 | 5 / 3 | |
| 0.2.7 | 5 / 3 | |
| 0.2.6 | 5 / 3 | |
| 0.2.5 | 5 / 3 | |
| 0.2.4 | 5 / 3 | |
| 0.2.3 | 5 / 3 | |
| 0.2.2 | 5 / 3 | |
| 0.2.1 | 5 / 3 | |
| 0.2.0 | 5 / 3 | |
| 0.1.2 | 4 / 2 | |
| 0.1.1 | 4 / 2 | |
| 0.1.0 | 4 / 2 |
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.