react-doctor
Diagnose and fix performance issues in your React app
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migrated from personal account to GitHub Actions CI/CD with SLSA provenance; legitimate transition. | ai | |
| phantom-deps | phantom-dep:deslop-js | AI (phantom-deps): Declared dep used as a tool/plugin, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:oxlint | AI (phantom-deps): oxlint is a runtime dependency for the diagnostics engine; declared correctly. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a runtime dependency for type checking; declared correctly. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): eslint plugin is a runtime dependency for linting; declared correctly. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.5.1 | 18 / 8 | |
| 0.5.0 | 18 / 8 | |
| 0.4.2 | 18 / 8 | |
| 0.4.1 | 18 / 8 | |
| 0.4.0 | 18 / 8 | |
| 0.3.0 | 15 / 7 | |
| 0.2.16 | 15 / 7 | |
| 0.2.15 | 15 / 7 | |
| 0.2.14 | 10 / 5 | |
| 0.2.13 | 10 / 5 | |
| 0.2.12 | 10 / 5 | |
| 0.2.11 | 10 / 5 | |
| 0.2.10 | 10 / 5 | |
| 0.2.9 | 10 / 5 | |
| 0.2.8 | 10 / 5 | |
| 0.2.7 | 10 / 5 | |
| 0.2.6 | 9 / 6 | |
| 0.2.5 | 9 / 6 | |
| 0.2.4 | 8 / 6 | |
| 0.2.2 | 5 / 7 | |
| 0.2.1 | 8 / 6 | |
| 0.2.0 | 8 / 6 | |
| 0.0.47 | 8 / 2 | |
| 0.0.46 | 8 / 2 | |
| 0.0.45 | 8 / 2 | |
| 0.0.44 | 7 / 2 | |
| 0.0.42 | 8 / 2 | |
| 0.0.41 | 8 / 2 | |
| 0.0.40 | 8 / 2 | |
| 0.0.39 | 8 / 2 | |
| 0.0.37 | 8 / 2 | |
| 0.0.36 | 8 / 2 | |
| 0.0.35 | 8 / 2 | |
| 0.0.34 | 8 / 2 | |
| 0.0.33 | 8 / 2 | |
| 0.0.32 | 8 / 2 | |
| 0.0.31 | 8 / 2 | |
| 0.0.3 | 3 / 1 | |
| 0.0.2 | 3 / 1 |
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-04. 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.
v0.2.16
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. 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.
v0.2.15
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. 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.
v0.2.14
2 findingsThis version was published by a different npm account than previous versions on 2026-05-30. 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.
v0.2.13
2 findingsThis version was published by a different npm account than previous versions on 2026-05-30. 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.
v0.2.12
2 findingsThis version was published by a different npm account than previous versions on 2026-05-30. 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.
v0.2.11
2 findingsThis version was published by a different npm account than previous versions on 2026-05-28. 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.
v0.2.10
2 findingsThis version was published by a different npm account than previous versions on 2026-05-28. 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.
v0.2.9
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. 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.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.