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
70 of your 163 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 87.02s for a 103.2 MB repo slow.
  • Repobility's analysis ran in 21.15s after the clone landed.

storybookjs/storybook

https://github.com/storybookjs/storybook · scanned 2026-06-05 06:59 UTC (6 days ago) · 10 languages

1148 raw signals (138 security + 1010 graph) 11/13 scanners ran 69th percentile · Typescript · large (100-500K LoC) System graph score 59 (higher by 20)

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

Complete repo analysis

Last scanned 6 days ago · v2 · 545 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
66.9
/100
Security checks
75
44 findings
System graph
59
100.0% cov · 501 findings
Critical
4
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 85.0 0.25 21.25
testing_score 72.0 0.20 14.40
documentation_score 87.0 0.15 13.05
practices_score 88.0 0.15 13.20
code_quality 80.0 0.10 8.00
Overall 1.00 78.9
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 4 High 43 Medium 45 Low 190 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 44 System graph 501 Crowd 0 Layer: Quality 151 Security 36 Software 53 Cicd 5 Frontend 270 Network 2 Api 28

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 6 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.
6 matching findings on this repo
  • info TODO/FIXME marker in shipping code — code/renderers/react/src/__test__/portable…
  • low Old/deprecated-named symbol `TSLegacy` in code/frameworks/svelte-vite/template/…
  • low Old/deprecated-named symbol `exampleLegacy` in code/frameworks/nextjs/src/font/…
  • low Old/deprecated-named symbol `IndexEntryLegacy` in code/core/src/types/modules/a…
  • low Old/deprecated-named symbol `IndexEntryLegacy` in code/core/src/preview-api/mod…
  • low Old/deprecated-named symbol `ImageLegacy` in test-storybooks/portable-stories-k…
View all legacy markers findings →
Commented-out code 75 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 (6 lines) in scripts/task.ts:135
  • info Commented-code block (6 lines) in scripts/event-log-checker.ts:82
  • info Commented-code block (6 lines) in scripts/eval/lib/run-trial.ts:77
  • info Commented-code block (8 lines) in scripts/ci/common-jobs.ts:54
  • info Commented-code block (5 lines) in code/playwright.config.ts:72
  • info Commented-code block (6 lines) in code/builders/builder-webpack5/src/preview/ba…
  • info Commented-code block (5 lines) in code/builders/builder-vite/src/vite-config.ts…
  • info Commented-code block (5 lines) in code/builders/builder-vite/src/plugins/storyb…
  • info Commented-code block (5 lines) in code/presets/create-react-app/src/index.ts:95
  • info Commented-code block (6 lines) in code/addons/pseudo-states/src/stories/NestedR…
  • info Commented-code block (5 lines) in code/addons/docs/template/stories/docspage/ov…
  • info Commented-code block (5 lines) in code/addons/docs/src/blocks/blocks/DocsContex…
View all commented-out code findings →
Config drift 22 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: vitest.config.ts
  • low File has no detected symbols: scripts/vitest.config.ts
  • low File has no detected symbols: scripts/eval/lib/agents/config.test.ts
  • info TODO/FIXME marker in shipping code — code/vitest.config.storybook.ts:41
  • info TODO/FIXME marker in shipping code — code/builders/builder-webpack5/src/preview…
  • info TODO/FIXME marker in shipping code — code/builders/builder-webpack5/src/preview…
  • info TODO/FIXME marker in shipping code — code/frameworks/nextjs/src/config/webpack.…
  • info TODO/FIXME marker in shipping code — code/core/src/common/utils/validate-config…
  • low Stray `console.log` in TS/JS — code/core/src/common/utils/log-config.ts:4
  • info TODO/FIXME marker in shipping code — code/core/src/common/utils/setup-addon-in-…
  • info TODO/FIXME marker in shipping code — code/core/src/csf-tools/ConfigFile.ts:147
  • high Insecure pattern 'exec_used' in code/lib/eslint-plugin/build-config.ts:9 code/lib/eslint-plugin/build-config.ts:9
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/ff7f66c4-126b-4c0f-896b-d5a9a906e679/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ff7f66c4-126b-4c0f-896b-d5a9a906e679/

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.