build(deps-dev): bump react-doctor from 0.5.8 to 0.7.2

[dependabot]

Bumps react-doctor from 0.5.8 to 0.7.2.

Release notes

Sourced from react-doctor's releases.

react-doctor@0.7.2

Patch Changes

• #1077 9cb4149 Thanks @​aidenybai! - Align 30+ rules with their documented behavior, fixing the false-positive clusters confirmed by a validation pass of 2,143 sampled diagnostics against the official rule prompts. Highlights: jsx-key now flags key-after-spread (the documented hazard) instead of the safe key-before-spread shape and exempts props rest parameters; no-did-update-set-state honors the prop-comparison guard exemption; no-console skips Node CLI scripts; circular-dependency skips type-only, lazy-import, and render-time-only cycles; query-mutation-missing-invalidation exempts read-only mutations; insecure-crypto-risk requires cryptographic context instead of matching identifier names; no-unknown-property allows valid hyphenated SVG attributes; no-aria-hidden-on-focusable verifies the element is actually focusable; no-flush-sync implements the documented DOM-measurement carve-out.

• #1069 5809083 Thanks @​rayhanadev! - Add --supply-chain / --no-supply-chain CLI flags to toggle the dependency supply-chain scan, mirroring --lint/--no-lint and --dead-code/--no-dead-code. Supply-chain enablement now resolves as a scan option (InspectOptions.supplyChain) against supplyChain.enabled — the flag wins — so it takes precedence over per-project config on every scan (a workspace module's config can't undo --no-supply-chain), and config isn't mutated so scan.hasCustomConfig telemetry stays accurate. The enabled state also rides the per-scan wide event as scan.supplyChain.

• #1083 5d2f17f Thanks @​skoshx! - query-destructure-result no longer classifies rest-destructuring (const { data, ...rest } = query) — that shape is query-no-rest-destructuring's territory, and claiming it in both rules reported the same line twice (#1082). The rule now fires only on the consumption it uniquely owns: spreading the whole TanStack Query result into JSX (<Inner {...query} />) or an object literal, which enumerates every field and subscribes the component to all of them.

• #1070 64452aa Thanks @​rayhanadev! - Fix whole-repo scan cache replaying another project's diagnostics when a .git-less checkout sits inside an unrelated repository (e.g. a gitignored benchmark/mining clone directory reused across projects). The cache key's git identity (HEAD sha, worktree fingerprint) resolved from the enclosing repository, which cannot see the checkout's files, so two different projects materialized at the same path keyed identically. The key now requires the fingerprinted repository to actually track files under the project directory (cache off otherwise), and every cache hit re-verifies the stored payload's directory and package.json content hash so any future keying bug of this class degrades to a miss instead of a cross-project replay.

• #1077 9cb4149 Thanks @​aidenybai! - Third-round FP sweep: honor eslint-disable react-hooks/<rule> spellings for React Compiler diagnostics, suppress immutability findings inside Reanimated worklets, skip the vulnerability axis for devDependencies in supply-chain scoring, suppress query-no-usequery-for-mutation for polled/read-verb POST endpoints, prune compile-time-erased edges from circular-dependency detection, and fix unused-export/unused-file/unused-dev-dependency false positives in deslop-js.

• Updated dependencies [9cb4149, 1880b15, 5d2f17f, 9cb4149]:

  • oxlint-plugin-react-doctor@0.7.2
  • deslop-js@0.7.2

react-doctor@0.7.1

Patch Changes

• #1062 6b21b70 Thanks @​devin-ai-integration! - Surface when a scan target had no discoverable React project, so a gated-off run can't pass for a clean one.

  • The JSON report now carries reactDetected: false (additive optional field on schemaVersion 1 and 2) when no scanned project resolved a React or Preact runtime — the case where every React-runtime rule family gates off and the report would otherwise be byte-indistinguishable from a genuinely clean scan. It's true when any project resolved a runtime, and absent when nothing was scanned or the run errored. Consumers gating on the report (CI, verifiers, pre-commit hooks) should treat reactDetected === false as "wrong scan target", not "all clear"; per-project detail is already available via projects[].project.reactVersion / preactVersion.
  • The CLI prints a stderr warning in the same case: "No React project detected at — React rules were gated off; this is not the same as a clean scan."
  • The programmatic API mirrors the signal: diagnose() results carry reactDetected (DiagnoseResult.reactDetected, per-project on ProjectResultOk, aggregate on DiagnoseProjectsResult — absent when no project scanned successfully), and the hasReactRuntime(project) predicate is exported from react-doctor/api and @react-doctor/api.

• Updated dependencies [c0c3fc1]:

  • oxlint-plugin-react-doctor@0.7.1
  • deslop-js@0.7.1

react-doctor@0.7.0

Patch Changes

• #1060 ced746f Thanks @​rayhanadev! - The whole cache stack now survives CI's fresh checkouts, so the GitHub Action's persisted REACT_DOCTOR_CACHE_DIR actually warms every layer instead of only the content-addressed ones. The whole-repo scan-result cache moves under the shared per-project cache root (honoring REACT_DOCTOR_CACHE_DIR like the lint, sidecar, dead-code, and supply-chain caches — previously it silently escaped the action's cache into node_modules/.cache or the OS temp dir), and its key drops every stat-based fingerprint that a re-clone rotates: config files and gitignored dotenv files are now content-hashed, and the toolchain is keyed by package versions (matching the lint ruleset hash) rather than install mtimes. The stat-fingerprinted dead-code caches gain mtime repair (the ninja/restat pattern): entries carry a content-hash witness, and a stat mismatch over identical bytes — every file after a fresh checkout — re-hashes once, accepts the entry, and persists the refreshed stat so the cost is paid once per checkout, not per run. This covers core's whole-project dead-code result cache (per-file (mtime, size, hash) records replacing the stats-in-key fingerprint) and deslop-js's incremental summary store (parse summaries, package-reference facts, and the manifest/bundler-config fingerprints feeding the collect/resolution hashes). Expired supply-chain score entries are also pruned past their TTL so restored cache directories stop accumulating dead purls. Everything stays fail-open and byte-identical to an uncached scan; on a re-cloned repo with one changed file, a warm scan now replays ~100% of lint, sidecar, and parse work instead of starting cold.

• #1056 20d81f6 Thanks @​rayhanadev! - Hardened the dead-code result cache key against two silent-staleness classes. The fingerprinted extension and manifest name lists are now imported from deslop-js/analyzed-inputs — a new dependency-free subpath export assembled from the same constants deslop's own readers consume — so a deslop upgrade that widens its walk can never under-invalidate the cache. And the key now includes @react-doctor/core's own version, so upgrading react-doctor re-analyzes instead of replaying cached diagnostics shaped by an older core's post-processing. The cache schema-version constant remains for cache-format changes only.

• #1053 e257a5e Thanks @​rayhanadev! - Rescans now skip the dead-code analysis entirely when nothing it reads has changed. The pass persists its diagnostics keyed by a fingerprint over the analyzed source tree (stat-based, so additions, deletions, and edits all invalidate), the project's manifests, tsconfigs, lockfiles, knip/entry/ignore configuration, and the analyzer version — on an unchanged-input rerun the stored result replays instead of re-walking the whole import graph, cutting several seconds off warm rescans of large repos. Only complete, successful passes are stored; REACT_DOCTOR_NO_CACHE (or the granular REACT_DOCTOR_NO_DEAD_CODE_CACHE) disables it.

• #1057 ce49250 Thanks @​rayhanadev! - Dead-code analysis is now incremental across scans. deslop-js gains an opt-in incrementalCachePath config field: one stat walk per run (following directory symlinks, like the glob scans it stands in for) validates four independently keyed layers — per-file parse summaries (mtime+size), the collected file list, the module-resolution map (dropped whenever the file set or a bundler/tsconfig-like config changes, since resolution is file-set-dependent), and the per-file package-reference facts behind the unused-dependency content scans. The same walk also answers the stale-package file-discovery globs (config/docs/rescue/package.json/nx/tsconfig scans, verified byte-identical against fast-glob), so a cached run never re-walks the tree for them. Entry resolution deliberately stays live every run (it reads config/doc/sibling-source content no fingerprint can validate); on cached runs it moves to a dedicated worker thread so its filesystem work overlaps the main-thread analysis instead of serializing after it. Every layer fails open — corrupt, truncated, or version/config-mismatched stores degrade to a fresh computation, never a wrong result — writes are atomic and skipped when clean, and results are byte-identical to an uncached run. Unused-export detection also indexes re-export edges by source module, dropping an O(entry points × edges) scan that dominated the detector on large repos.

  react-doctor points the analysis worker at a per-project summary store next to the existing whole-result dead-code cache, so a changed-files rescan of a large repo re-parses only what changed (sentry, 9k files: ~8.0s → ~3.2s with 0-10 files edited; ~4.0s after adding a file; the cache-fill run costs the same as an uncached scan). The worker also stops running the discarded DRY-pattern redundancy detectors (reportRedundancy: false), which shrinks the summary store by dropping fields only those detectors read, and reports the cache outcome as deadCode.summaryCacheHits / deadCode.summaryCacheMisses in anonymized telemetry (absent whenever no analysis consulted the store). REACT_DOCTOR_NO_CACHE (or the granular REACT_DOCTOR_NO_DEAD_CODE_CACHE) disables it.

• #1054 8c004f0 Thanks @​rayhanadev! - Instant reruns now also work with uncommitted changes: the whole-repo scan-result cache no longer requires a clean worktree — it keys on the exact dirty state (every modified, staged, renamed, deleted, and untracked path plus a hash of its content), so rescanning the same work-in-progress tree hits the cache while any edit still invalidates it.

• #1052 1571119 Thanks @​rayhanadev! - Restore instant reruns on large repos: raise runGit's output cap so the whole-repo scan-result cache works past ~15k tracked files.

  The cache's clean-worktree gates shell out to git through a helper that used Node's default 1 MiB maxBuffer. On repos with roughly 15-25k tracked files (getsentry/sentry: 20,343), git ls-files -v alone exceeds that, execFileSync throws ENOBUFS, the helper swallows it into null, and the gates read null as "hidden tracked state" — so the cache silently never stored or served a scan on exactly the repos where the instant-rerun path saves the most time. The helper now runs with an explicit 64 MiB cap, which clears monorepos with hundreds of thousands of files while still bounding a pathological child process.

• #1058 ea9a775 Thanks @​rayhanadev! - Warm rescans now skip the cross-file lint sidecar for files whose dependencies are unchanged. Previously the per-file lint cache replayed most rules but re-linted EVERY file with the cross-file ruleset (no-barrel-import, the Next.js metadata/Suspense rules, no-mutating-reducer-state, the React Native text rules) on every scan, because a sibling edit can flip an unchanged file's verdict. Each file now carries a dependency fingerprint — the exact set of filesystem probes (resolved import targets, barrel chains, ancestor layouts, nearest package.json/tsconfig, and the negative resolution candidates that catch shadowing) its cross-file rules consulted — and the sidecar replays the stored diagnostics when every probe still answers the same, re-linting only files whose dependency set changed. Every entry fails open (corrupt store, unparseable file, partial lint → fresh re-lint), a cross-file rule without a registered dependency collector re-lints everywhere, and REACT_DOCTOR_NO_CACHE (or the granular REACT_DOCTOR_NO_SIDECAR_CACHE) disables it.

... (truncated)

Changelog

Sourced from react-doctor's changelog.

0.7.2

Patch Changes

• #1077 9cb4149 Thanks @​aidenybai! - Align 30+ rules with their documented behavior, fixing the false-positive clusters confirmed by a validation pass of 2,143 sampled diagnostics against the official rule prompts. Highlights: jsx-key now flags key-after-spread (the documented hazard) instead of the safe key-before-spread shape and exempts props rest parameters; no-did-update-set-state honors the prop-comparison guard exemption; no-console skips Node CLI scripts; circular-dependency skips type-only, lazy-import, and render-time-only cycles; query-mutation-missing-invalidation exempts read-only mutations; insecure-crypto-risk requires cryptographic context instead of matching identifier names; no-unknown-property allows valid hyphenated SVG attributes; no-aria-hidden-on-focusable verifies the element is actually focusable; no-flush-sync implements the documented DOM-measurement carve-out.

• #1069 5809083 Thanks @​rayhanadev! - Add --supply-chain / --no-supply-chain CLI flags to toggle the dependency supply-chain scan, mirroring --lint/--no-lint and --dead-code/--no-dead-code. Supply-chain enablement now resolves as a scan option (InspectOptions.supplyChain) against supplyChain.enabled — the flag wins — so it takes precedence over per-project config on every scan (a workspace module's config can't undo --no-supply-chain), and config isn't mutated so scan.hasCustomConfig telemetry stays accurate. The enabled state also rides the per-scan wide event as scan.supplyChain.

• #1083 5d2f17f Thanks @​skoshx! - query-destructure-result no longer classifies rest-destructuring (const { data, ...rest } = query) — that shape is query-no-rest-destructuring's territory, and claiming it in both rules reported the same line twice (#1082). The rule now fires only on the consumption it uniquely owns: spreading the whole TanStack Query result into JSX (<Inner {...query} />) or an object literal, which enumerates every field and subscribes the component to all of them.

• #1070 64452aa Thanks @​rayhanadev! - Fix whole-repo scan cache replaying another project's diagnostics when a .git-less checkout sits inside an unrelated repository (e.g. a gitignored benchmark/mining clone directory reused across projects). The cache key's git identity (HEAD sha, worktree fingerprint) resolved from the enclosing repository, which cannot see the checkout's files, so two different projects materialized at the same path keyed identically. The key now requires the fingerprinted repository to actually track files under the project directory (cache off otherwise), and every cache hit re-verifies the stored payload's directory and package.json content hash so any future keying bug of this class degrades to a miss instead of a cross-project replay.

• #1077 9cb4149 Thanks @​aidenybai! - Third-round FP sweep: honor eslint-disable react-hooks/<rule> spellings for React Compiler diagnostics, suppress immutability findings inside Reanimated worklets, skip the vulnerability axis for devDependencies in supply-chain scoring, suppress query-no-usequery-for-mutation for polled/read-verb POST endpoints, prune compile-time-erased edges from circular-dependency detection, and fix unused-export/unused-file/unused-dev-dependency false positives in deslop-js.

• Updated dependencies [9cb4149, 1880b15, 5d2f17f, 9cb4149]:

  • oxlint-plugin-react-doctor@0.7.2
  • deslop-js@0.7.2

0.7.1

Patch Changes

• #1062 6b21b70 Thanks @​devin-ai-integration! - Surface when a scan target had no discoverable React project, so a gated-off run can't pass for a clean one.

  • The JSON report now carries reactDetected: false (additive optional field on schemaVersion 1 and 2) when no scanned project resolved a React or Preact runtime — the case where every React-runtime rule family gates off and the report would otherwise be byte-indistinguishable from a genuinely clean scan. It's true when any project resolved a runtime, and absent when nothing was scanned or the run errored. Consumers gating on the report (CI, verifiers, pre-commit hooks) should treat reactDetected === false as "wrong scan target", not "all clear"; per-project detail is already available via projects[].project.reactVersion / preactVersion.
  • The CLI prints a stderr warning in the same case: "No React project detected at — React rules were gated off; this is not the same as a clean scan."
  • The programmatic API mirrors the signal: diagnose() results carry reactDetected (DiagnoseResult.reactDetected, per-project on ProjectResultOk, aggregate on DiagnoseProjectsResult — absent when no project scanned successfully), and the hasReactRuntime(project) predicate is exported from react-doctor/api and @react-doctor/api.

• Updated dependencies [c0c3fc1]:

  • oxlint-plugin-react-doctor@0.7.1
  • deslop-js@0.7.1

0.7.0

Patch Changes

• #1060 ced746f Thanks @​rayhanadev! - The whole cache stack now survives CI's fresh checkouts, so the GitHub Action's persisted REACT_DOCTOR_CACHE_DIR actually warms every layer instead of only the content-addressed ones. The whole-repo scan-result cache moves under the shared per-project cache root (honoring REACT_DOCTOR_CACHE_DIR like the lint, sidecar, dead-code, and supply-chain caches — previously it silently escaped the action's cache into node_modules/.cache or the OS temp dir), and its key drops every stat-based fingerprint that a re-clone rotates: config files and gitignored dotenv files are now content-hashed, and the toolchain is keyed by package versions (matching the lint ruleset hash) rather than install mtimes. The stat-fingerprinted dead-code caches gain mtime repair (the ninja/restat pattern): entries carry a content-hash witness, and a stat mismatch over identical bytes — every file after a fresh checkout — re-hashes once, accepts the entry, and persists the refreshed stat so the cost is paid once per checkout, not per run. This covers core's whole-project dead-code result cache (per-file (mtime, size, hash) records replacing the stats-in-key fingerprint) and deslop-js's incremental summary store (parse summaries, package-reference facts, and the manifest/bundler-config fingerprints feeding the collect/resolution hashes). Expired supply-chain score entries are also pruned past their TTL so restored cache directories stop accumulating dead purls. Everything stays fail-open and byte-identical to an uncached scan; on a re-cloned repo with one changed file, a warm scan now replays ~100% of lint, sidecar, and parse work instead of starting cold.

• #1056 20d81f6 Thanks @​rayhanadev! - Hardened the dead-code result cache key against two silent-staleness classes. The fingerprinted extension and manifest name lists are now imported from deslop-js/analyzed-inputs — a new dependency-free subpath export assembled from the same constants deslop's own readers consume — so a deslop upgrade that widens its walk can never under-invalidate the cache. And the key now includes @react-doctor/core's own version, so upgrading react-doctor re-analyzes instead of replaying cached diagnostics shaped by an older core's post-processing. The cache schema-version constant remains for cache-format changes only.

• #1053 e257a5e Thanks @​rayhanadev! - Rescans now skip the dead-code analysis entirely when nothing it reads has changed. The pass persists its diagnostics keyed by a fingerprint over the analyzed source tree (stat-based, so additions, deletions, and edits all invalidate), the project's manifests, tsconfigs, lockfiles, knip/entry/ignore configuration, and the analyzer version — on an unchanged-input rerun the stored result replays instead of re-walking the whole import graph, cutting several seconds off warm rescans of large repos. Only complete, successful passes are stored; REACT_DOCTOR_NO_CACHE (or the granular REACT_DOCTOR_NO_DEAD_CODE_CACHE) disables it.

• #1057 ce49250 Thanks @​rayhanadev! - Dead-code analysis is now incremental across scans. deslop-js gains an opt-in incrementalCachePath config field: one stat walk per run (following directory symlinks, like the glob scans it stands in for) validates four independently keyed layers — per-file parse summaries (mtime+size), the collected file list, the module-resolution map (dropped whenever the file set or a bundler/tsconfig-like config changes, since resolution is file-set-dependent), and the per-file package-reference facts behind the unused-dependency content scans. The same walk also answers the stale-package file-discovery globs (config/docs/rescue/package.json/nx/tsconfig scans, verified byte-identical against fast-glob), so a cached run never re-walks the tree for them. Entry resolution deliberately stays live every run (it reads config/doc/sibling-source content no fingerprint can validate); on cached runs it moves to a dedicated worker thread so its filesystem work overlaps the main-thread analysis instead of serializing after it. Every layer fails open — corrupt, truncated, or version/config-mismatched stores degrade to a fresh computation, never a wrong result — writes are atomic and skipped when clean, and results are byte-identical to an uncached run. Unused-export detection also indexes re-export edges by source module, dropping an O(entry points × edges) scan that dominated the detector on large repos.

  react-doctor points the analysis worker at a per-project summary store next to the existing whole-result dead-code cache, so a changed-files rescan of a large repo re-parses only what changed (sentry, 9k files: ~8.0s → ~3.2s with 0-10 files edited; ~4.0s after adding a file; the cache-fill run costs the same as an uncached scan). The worker also stops running the discarded DRY-pattern redundancy detectors (reportRedundancy: false), which shrinks the summary store by dropping fields only those detectors read, and reports the cache outcome as deadCode.summaryCacheHits / deadCode.summaryCacheMisses in anonymized telemetry (absent whenever no analysis consulted the store). REACT_DOCTOR_NO_CACHE (or the granular REACT_DOCTOR_NO_DEAD_CODE_CACHE) disables it.

• #1054 8c004f0 Thanks @​rayhanadev! - Instant reruns now also work with uncommitted changes: the whole-repo scan-result cache no longer requires a clean worktree — it keys on the exact dirty state (every modified, staged, renamed, deleted, and untracked path plus a hash of its content), so rescanning the same work-in-progress tree hits the cache while any edit still invalidates it.

• #1052 1571119 Thanks @​rayhanadev! - Restore instant reruns on large repos: raise runGit's output cap so the whole-repo scan-result cache works past ~15k tracked files.

... (truncated)

Commits

• aa519e5 chore: version packages (#1068)
• 9cb4149 fix(oxlint-plugin): precision sweep — narrow 40+ rules against verified FPs f...
• 5809083 feat(cli): add --supply-chain / --no-supply-chain to toggle the dependency sc...
• 64452aa fix(cli): scan cache no longer replays across projects at a reused path (#1070)
• 160f84c chore: version packages (#1063)
• 6b21b70 feat(core): surface reactDetected so a gated-off scan can't pass for clean (#...
• 574cba6 chore: version packages (#1055)
• ced746f fix(core): make the cache stack survive CI checkouts and the action cache (#1...
• bdf8074 feat(telemetry): classify every scan's cache temperature in the wide event (#...
• ea9a775 perf(core): incremental cross-file sidecar lint via dependency probe traces (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

This is a Dependabot PR updating the react-doctor dev dependency from 0.5.8 to 0.7.2. The changes are limited to:

1. package.json - version bump only (line 62-65)
2. pnpm-lock.yaml - auto-generated lock file updates

No application code changes are present. This is a routine dependency update that can be safely merged.

Files Reviewed (2 files)

• package.json - 0 issues (version bump only)
• pnpm-lock.yaml - 0 issues (auto-generated)

---

_{Reviewed by laguna-m.1-20260312 · Input: 33.9K · Output: 2.1K · Cached: 239.8K}

[dependabot]

Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request.

[dependabot]

Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request.

[dependabot]

Superseded by #208.