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
53 of your 134 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

inngest/inngest

https://github.com/inngest/inngest · scanned 2026-06-05 14:18 UTC (5 days, 5 hours ago) · 10 languages

664 raw signals (128 security + 536 graph) 11/13 scanners ran 61st percentile · Go · large (100-500K LoC) System graph score 68 (higher by 16)

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

Complete repo analysis

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

JSON
Combined
78.6
/100
Security checks
90
62 findings
System graph
68
100.0% cov · 219 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 85.0 0.20 17.00
documentation_score 63.0 0.15 9.45
practices_score 82.0 0.15 12.30
code_quality 70.0 0.10 7.00
Overall 1.00 83.5
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 35 Medium 19 Low 114 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 62 System graph 219 Crowd 0 Layer: Quality 87 Security 27 Cicd 12 Software 56 Frontend 93 Hardware 6

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.

Legacy markers 7 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
7 matching findings on this repo
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/dashboard/src/components/Bill…
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/dashboard/src/gql/graphql.ts:…
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/dashboard/src/gql/gql.ts:137
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/dashboard/src/routes/_authed/…
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/dashboard/src/queries/server/…
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/support/src/gql/graphql.ts:257
  • low Old/deprecated-named symbol `isLegacy` in ui/apps/support/src/gql/gql.ts:74
View all legacy markers findings →
Commented-out code 12 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 docs/api-docs/src/shims/node-path.ts:1
  • info Commented-code block (5 lines) in ui/apps/dashboard/src/components/Insights/use…
  • info Commented-code block (5 lines) in ui/apps/dashboard/src/components/Insights/Ins…
  • info Commented-code block (5 lines) in ui/apps/dashboard/src/components/Experiments/…
  • info Commented-code block (12 lines) in ui/apps/dashboard/src/components/SeatOverage…
  • info Commented-code block (13 lines) in ui/apps/dashboard/src/components/BillingBann…
  • info Commented-code block (5 lines) in ui/apps/dashboard/src/components/APIKeys/Crea…
  • info Commented-code block (7 lines) in ui/apps/dashboard/src/components/Layout/SideB…
  • info Commented-code block (6 lines) in ui/packages/components/src/Events/EventsTable…
  • info Commented-code block (10 lines) in ui/packages/components/src/SchemaViewer/tran…
  • info Commented-code block (10 lines) in ui/packages/components/src/hooks/useCron.tes…
  • info Commented-code block (5 lines) in ui/packages/components/src/RunsPage/RunsPage.…
View all commented-out code findings →
Config drift 14 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 File has no detected symbols: tests/js/next.config.js
  • low File has no detected symbols: docs/api-docs/vite.config.ts
  • low File has no detected symbols: docs/api-docs/source.config.ts
  • low File has no detected symbols: ui/apps/dashboard/vite.config.ts
  • low File has no detected symbols: ui/apps/dashboard/tailwind.config.ts
  • low File has no detected symbols: ui/apps/dashboard/graphql.config.ts
  • low File has no detected symbols: ui/apps/dashboard/vitest.config.ts
  • info TODO/FIXME marker in shipping code — ui/apps/dashboard/vite.config.ts:24
  • info `truncate` class without `title=` for hover reveal — ui/apps/dashboard/src/comp…
  • info TODO/FIXME marker in shipping code — ui/apps/dev-server-ui/vite.config.ts:76
  • info `truncate` class without `title=` for hover reveal — ui/packages/components/src…
  • info `truncate` class without `title=` for hover reveal — ui/packages/components/src…
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/dff1705c-35ea-414c-a352-2231a387a0c4/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dff1705c-35ea-414c-a352-2231a387a0c4/

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.