Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo
64 of your 100 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 57.23s for a 77.1 MB repo slow.
  • Repobility's analysis ran in 8.64s after the clone landed.

inaturalist/iNaturalistReactNative

https://github.com/inaturalist/iNaturalistReactNative · scanned 2026-06-05 17:56 UTC (4 days, 21 hours ago) · 10 languages

603 raw signals (93 security + 510 graph) 11/13 scanners ran 92nd percentile · Typescript · medium (20-100K LoC) System graph score 70 (higher by 16)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 21 hours ago · v2 · 250 actionable findings from 2 signal sources. 98 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
80.5
/100
Security checks
91
25 findings
System graph
70
100.0% cov · 225 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 55.0 0.15 8.25
practices_score 84.0 0.15 12.60
code_quality 80.0 0.10 8.00
Overall 1.00 86.6
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 5 Medium 7 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 25 System graph 225 Crowd 0 Layer: Quality 78 Security 2 Software 56 Cicd 4 Frontend 105 Api 5

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 57 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
12 matching findings on this repo
  • info Commented-code block (10 lines) in .eslintrc.js:52
  • info Commented-code block (5 lines) in react-native-logs.config.ts:49
  • info Commented-code block (5 lines) in index.js:90
  • info Commented-code block (5 lines) in tests/realm.setup.js:7
  • info Commented-code block (14 lines) in tests/integration/MyObservations.test.js:147
  • info Commented-code block (5 lines) in tests/integration/MyObservationsLocalization.…
  • info Commented-code block (7 lines) in tests/integration/navigation/MediaViewer.test…
  • info Commented-code block (9 lines) in tests/integration/navigation/Explore.test.js:…
  • info Commented-code block (8 lines) in tests/integration/navigation/broken/MyObserva…
  • info Commented-code block (7 lines) in tests/integration/navigation/broken/Suggestio…
  • info Commented-code block (13 lines) in tests/integration/navigation/broken/AICamera…
  • info Commented-code block (24 lines) in tests/integration/broken/SuggestionsWithUnsy…
View all commented-out code findings →
Config drift 7 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
7 matching findings on this repo
  • low File has no detected symbols: metro.config.js
  • low File has no detected symbols: babel.config.js
  • low File has no detected symbols: tailwind.config.js
  • low File has no detected symbols: jest.config.ts
  • low File has no detected symbols: react-native.config.js
  • low File has no detected symbols: react-native-logs.config.ts
  • info Commented-code block (5 lines) in react-native-logs.config.ts:49
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/129646b0-fda5-48da-bc79-681a24fab2c2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/129646b0-fda5-48da-bc79-681a24fab2c2/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.