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.

shakacode/react_on_rails

https://github.com/shakacode/react_on_rails · scanned 2026-06-16 00:09 UTC (2 months, 2 weeks ago)

363 raw signals (0 security + 363 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 234 actionable findings from 1 signal source. 129 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 234 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 9 High 13 Medium 55 Low 79 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 234 Crowd 0 Layer: Frontend 67 Hardware 4 Security 46 Cicd 5 Quality 99 Api 13

Exclude dismissed / FP Exclude test files

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 66 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 (5 lines) in react_on_rails/spec/dummy/babel.config.js:29
info Commented-code block (5 lines) in react_on_rails/spec/dummy/client/app/strictMo…
info Commented-code block (5 lines) in react_on_rails/spec/dummy/client/app/startup/…
info Commented-code block (5 lines) in react_on_rails/spec/dummy/client/app/startup/…
info Commented-code block (9 lines) in react_on_rails/spec/dummy/client/app/packs/cl…
info Commented-code block (6 lines) in react_on_rails/spec/dummy/config/webpack/alia…
info Commented-code block (5 lines) in react_on_rails/lib/generators/react_on_rails/…
info Commented-code block (5 lines) in react_on_rails/lib/generators/react_on_rails/…
info Commented-code block (5 lines) in docs/sidebars.ts:3
info Commented-code block (8 lines) in packages/react-on-rails/tests/pageLifecycle.t…
info Commented-code block (5 lines) in packages/react-on-rails/tests/ClientRenderer.…
info Commented-code block (9 lines) in packages/react-on-rails/tests/serverRenderRea…

View all commented-out code findings →

Config drift 24 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.

12 matching findings on this repo

low Stray `console.log` in TS/JS — react_on_rails/spec/dummy/config/webpack/webpack…
info TODO/FIXME marker in shipping code — react_on_rails/spec/dummy/config/webpack/a…
low Stray `console.log` in TS/JS — react_on_rails/spec/dummy/config/webpack/webpack…
low Stray `console.log` in TS/JS — react_on_rails_pro/spec/dummy/config/webpack/Ser…
low Stray `console.log` in TS/JS — react_on_rails_pro/spec/dummy/config/webpack/web…
low Stray `console.log` in TS/JS — react_on_rails_pro/spec/execjs-compatible-dummy/…
low Stray `console.log` in TS/JS — react_on_rails_pro/spec/execjs-compatible-dummy/…
medium Insecure pattern 'cors_wildcard' in react_on_rails/spec/dummy/config/shakapacke… react_on_rails/spec/dummy/config/shakapacker.yml:62
critical Possible secret in packages/react-on-rails-pro-node-renderer/src/shared/configB… packages/react-on-rails-pro-node-renderer/src/sha…:366
medium Insecure pattern 'cors_wildcard' in react_on_rails_pro/spec/dummy/config/shakap… react_on_rails_pro/spec/dummy/config/shakapacker.…:79
critical Possible secret in react_on_rails_pro/spec/dummy/config/initializers/react_on_r… react_on_rails_pro/spec/dummy/config/initializers…:30
medium Insecure pattern 'cors_wildcard' in react_on_rails_pro/spec/execjs-compatible-d… react_on_rails_pro/spec/execjs-compatible-dummy/c…:57

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/ba5c8749-6593-4668-8546-ac87a95f88c6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ba5c8749-6593-4668-8546-ac87a95f88c6/

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.