@rnx-kit/oxlint-config
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rnx-kit/eslint-plugin | AI (phantom-deps): Shareable config packages declare ESLint plugins as deps for consumers without importing them directly. This is standard practice and not a real phantom dep issue. | ai | |
| phantom-deps | phantom-dep:@react-native/eslint-plugin | AI (phantom-deps): Same rationale: config package declares ESLint plugin as a dependency for consumers, not for direct import. Expected pattern for shareable configs. | ai |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.