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.
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)

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
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in scripts/run-registry.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in scripts/run-registry.ts:215; move to env var / secrets manager.
scripts/run-registry.ts:215
#2
.env file present in repo: .env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#3
Insecure pattern 'exec_used' in scripts/build-package.ts:157
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/build-package.ts:157
#4
Insecure pattern 'exec_used' in scripts/prepare-sandbox.ts:73
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/prepare-sandbox.ts:73
#5
Insecure pattern 'exec_used' in scripts/run-registry.ts:167
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/run-registry.ts:167
#6
Insecure pattern 'exec_used' in scripts/utils/yarn.ts:76
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/utils/yarn.ts:76
#7
Insecure pattern 'exec_used' in scripts/utils/cli-step.ts:126
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/utils/cli-step.ts:126
#8
Insecure pattern 'exec_used' in scripts/tasks/smoke-test.ts:13
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/tasks/smoke-test.ts:13
#9
Insecure pattern 'exec_used' in scripts/tasks/compile.ts:35
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/tasks/compile.ts:35
#10
Insecure pattern 'exec_used' in scripts/tasks/sandbox-parts.ts:154
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/tasks/sandbox-parts.ts:154

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.