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.
93 of your 201 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 32.77s for a 83.1 MB repo slow.
  • Repobility's analysis ran in 48.97s after the clone landed.

vellum-ai/vellum-assistant

https://github.com/vellum-ai/vellum-assistant · scanned 2026-06-05 19:05 UTC (4 days, 18 hours ago) · 10 languages

3754 raw signals (178 security + 3576 graph) 11/13 scanners ran 46th percentile · Typescript · huge (>500K LoC) System graph score 52 (higher by 32)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v2 · 1835 actionable findings from 2 signal sources. 106 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 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 95.0 0.20 19.00
documentation_score 98.0 0.15 14.70
practices_score 78.0 0.15 11.70
code_quality 69.0 0.10 6.90
Overall 1.00 83.3
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

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.

Duplicates & near-duplicates 1 finding
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
1 matching finding on this repo
  • low Near-duplicate function bodies in 3 places
View all duplicates & near-duplicates findings →
Legacy markers 17 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.
12 matching findings on this repo
  • low Old/deprecated-named symbol `nudgeLegacy` in apps/web/src/utils/storage-migrati…
  • low Old/deprecated-named symbol `nudgeLegacy` in apps/web/src/utils/storage-migrati…
  • low Old/deprecated-named symbol `uploadAvatarImageLegacy` in apps/web/src/assistant…
  • low Old/deprecated-named symbol `credits_legacy` in apps/web/src/domains/settings/c…
  • low Old/deprecated-named symbol `asst_legacy` in packages/local-mode/src/lockfile.t…
  • low Old/deprecated-named symbol `ghp_legacy` in assistant/src/__tests__/credential-…
  • low Old/deprecated-named symbol `isLegacy` in assistant/src/ipc/ipc-framing.ts:142
  • low Old/deprecated-named symbol `isLegacy` in assistant/src/ipc/assistant-server.ts…
  • low Old/deprecated-named symbol `isLegacy` in assistant/src/ipc/__tests__/streaming…
  • low Old/deprecated-named symbol `allowFlatLegacy` in assistant/src/daemon/conversat…
  • low Old/deprecated-named symbol `allowFlatLegacy` in assistant/src/messaging/provid…
  • low Old/deprecated-named symbol `allowFlatLegacy` in assistant/src/messaging/provid…
View all legacy markers findings →
Commented-out code 984 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 (8 lines) in credential-executor/src/cli.ts:34
  • info Commented-code block (7 lines) in credential-executor/src/managed-main.ts:140
  • info Commented-code block (5 lines) in credential-executor/src/__tests__/http-policy…
  • info Commented-code block (5 lines) in credential-executor/src/__tests__/command-wor…
  • info Commented-code block (5 lines) in credential-executor/src/__tests__/ces-migrati…
  • info Commented-code block (5 lines) in credential-executor/src/__tests__/command-exe…
  • info Commented-code block (5 lines) in credential-executor/src/__tests__/managed-int…
  • info Commented-code block (5 lines) in credential-executor/src/commands/executor.ts:…
  • info Commented-code block (5 lines) in credential-executor/src/commands/validator.ts…
  • info Commented-code block (6 lines) in credential-executor/src/commands/workspace.ts…
  • info Commented-code block (5 lines) in credential-executor/src/http/path-template.ts…
  • info Commented-code block (5 lines) in credential-executor/src/materializers/local-s…
View all commented-out code findings →
Config drift 45 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: apps/web/capacitor.config.ts
  • low File has no detected symbols: apps/web/openapi-ts.config.ts
  • low File has no detected symbols: apps/web/src/components/charts/chart-config.ts
  • low Stray `console.log` in TS/JS — skills/resend-setup/scripts/check-config.ts:22
  • low Stray `console.log` in TS/JS — skills/mailgun-setup/scripts/check-config.ts:22
  • low Stray `console.log` in TS/JS — skills/stripe-app-setup/scripts/check-config.ts:…
  • low Stray `console.log` in TS/JS — skills/sentry-app-setup/scripts/check-config.ts:…
  • low Stray `console.log` in TS/JS — skills/discord-app-setup/scripts/check-config.ts…
  • low Very large file: assistant/src/__tests__/config-schema.test.ts (2402 lines)
  • info Commented-code block (5 lines) in apps/web/capacitor.config.ts:27
  • info Commented-code block (5 lines) in apps/macos/electron.vite.config.ts:13
  • info Commented-code block (5 lines) in cli/src/__tests__/assistant-config.test.ts:669
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/87dd9975-69d1-4959-b9b8-94465869ab20/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/87dd9975-69d1-4959-b9b8-94465869ab20/

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.