@react-native/eslint-config

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

react-native-botfb

Keywords

eslintconfigreact-native

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:shared.js	AI (source-diff): shared.js is a static ESLint config; the net-exec detection is a false positive for this package.	ai	2026/05/06
publish-pattern	dormant-publish	AI (publish-pattern): Backport patch releases for older minor series naturally have long gaps; trusted publisher with 1561 approved packages.	ai	2026/04/30
provenance	no-provenance	AI (provenance): Official React Native monorepo package; lack of Sigstore provenance is consistent across all versions and not a meaningful risk signal here.	ai	2026/04/30
phantom-deps	phantom-dep:@babel/eslint-parser	AI (phantom-deps): ESLint config packages reference parsers by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-plugin-ft-flow	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-config-prettier	AI (phantom-deps): ESLint config packages reference configs by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): ESLint config packages reference parsers by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-plugin-react-hooks	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-plugin-react-native	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@react-native/eslint-plugin	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-plugin-eslint-comments	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@typescript-eslint/eslint-plugin	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-plugin-jest	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-plugin-react	AI (phantom-deps): ESLint config packages reference plugins by name in config, not via import; stable false positive for this package.	ai	2026/04/30
dependencies	unvetted-dep:eslint-plugin-ft-flow	AI (dependencies): eslint-plugin-ft-flow is a legitimate Flow linting plugin; appropriate dependency for React Native ESLint config.	ai	2026/04/30
phantom-deps	phantom-dep:@babel/core	AI (phantom-deps): @babel/core is a declared runtime dep used by @babel/eslint-parser; phantom-dep false positive for this package.	ai	2026/04/29

Versions (showing 30 of 30)

Version	Deps	Published
0.85.3	12 / 2	2026-05-05
0.85.2	12 / 2	2026-04-20
0.85.1	12 / 2	2026-04-13
0.85.0	12 / 2	2026-04-07
0.84.1	12 / 2	2026-02-27
0.83.9	12 / 2	2026-04-27
0.83.8	12 / 2	2026-04-24
0.83.7	12 / 2	2026-04-24
0.83.6	12 / 2	2026-04-16
0.83.5	12 / 2	2026-04-13
0.83.0	12 / 2	2025-12-10
0.82.1	12 / 2	2025-10-20
0.82.0	12 / 2	2025-10-07
0.81.5	12 / 2	2025-10-21
0.81.4	12 / 2	2025-09-10
0.81.3	12 / 2	2025-09-10
0.81.2	12 / 2	2025-09-09
0.81.1	12 / 2	2025-08-27
0.81.0	12 / 2	2025-08-12
0.80.2	12 / 2	2025-07-24
0.80.1	12 / 2	2025-06-30
0.80.0	12 / 2	2025-06-12
0.79.7	12 / 2	2025-10-21
0.79.6	12 / 2	2025-08-14
0.79.5	12 / 2	2025-07-01
0.79.4	12 / 2	2025-06-17
0.79.3	12 / 2	2025-06-04
0.79.2	12 / 2	2025-05-01
0.78.3	12 / 2	2025-07-09
0.77.3	12 / 2	2025-07-21

v0.85.3

2 findings

HIGH New file with network + code execution: shared.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.85.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.85.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.85.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.84.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.83.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.83.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.83.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.83.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.83.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.83.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.82.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.82.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.81.5

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.81.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.81.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.81.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.81.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.81.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.80.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.80.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.80.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.79.7

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.79.6

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.79.5

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.79.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.79.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.79.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.78.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.77.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.