dust-tt/dust

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.

49 of your 75 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

https://github.com/dust-tt/dust · scanned 2026-06-05 15:16 UTC (5 days, 2 hours ago) · 10 languages

3007 raw signals (69 security + 2938 graph) 11/13 scanners ran 30th percentile · Typescript · medium (20-100K LoC) System graph score 60 (higher by 3)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 2 hours ago · v2 · 1500 actionable findings from 2 signal sources. 38 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 · 1457 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	20.0	0.20	4.00
`documentation_score`	42.0	0.15	6.30
`practices_score`	69.0	0.15	10.35
`code_quality`	80.0	0.10	8.00
Overall		1.00	62.6

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 266 Medium 85 Low 502 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 43 System graph 1457 Crowd 0 Layer: Software 57 Quality 539 Cicd 4 Frontend 590 Hardware 8 Security 21 Api 281

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.

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

View all duplicates & near-duplicates findings →

Legacy markers 26 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 Stray `console.log` in TS/JS — front/scripts/migrate_legacy_manual_internal_mcp…
low Stray `console.log` in TS/JS — front/mailing/20250724_slackstorm_legacy_users.t…
low Old/deprecated-named symbol `slackIsLegacy` in front-api/routes/w/[wId]/credent…
low Old/deprecated-named symbol `getLegacy` in front-api/routes/w/[wId]/credentials…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/google_a…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/mistral.…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/together…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/noop.ts:…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/firework…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/openai.t…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/deepseek…
low Old/deprecated-named symbol `isLegacy` in front/types/assistant/models/types.te…

View all legacy markers findings →

Commented-out code 307 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 connectors/migrations/20240111_batch_resync_g…
info Commented-code block (7 lines) in connectors/migrations/20231109_incident_gdriv…
info Commented-code block (10 lines) in connectors/migrations/20240719_migrate_nango…
info Commented-code block (6 lines) in connectors/migrations/20240110_batch_resync_n…
info Commented-code block (11 lines) in connectors/migrations/20241216_backfill_ms_f…
info Commented-code block (6 lines) in connectors/migrations/20230606_deprecate_nang…
info Commented-code block (11 lines) in connectors/migrations/20250110_investigate_z…
info Commented-code block (6 lines) in connectors/migrations/20230828_notion_block_p…
info Commented-code block (5 lines) in connectors/migrations/20241212_restore_gdrive…
info Commented-code block (16 lines) in connectors/migrations/20241211_fix_gdrive_pa…
info Commented-code block (7 lines) in connectors/src/types/content_nodes.ts:3
info Commented-code block (5 lines) in connectors/src/connectors/github/lib/code/fil…

View all commented-out code findings →

Config drift 68 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

high [MINED113] Express POST /connectors/:connector_id/config/:config_key has no aut… connectors/src/api_server.ts:195
high [MINED113] Express PATCH /connectors/:connector_id/configuration has no auth: E… connectors/src/api_server.ts:189
low File has no detected symbols: connectors/src/types/data_source_config.ts
low File has no detected symbols: connectors/src/connectors/bigquery/temporal/confi…
low File has no detected symbols: connectors/src/connectors/gong/temporal/config.ts
low File has no detected symbols: connectors/src/connectors/zendesk/temporal/config…
low Stray `console.log` in TS/JS — sdks/js/esbuild.config.ts:37
low Stray `console.log` in TS/JS — connectors/esbuild.config.ts:35
low Stray `console.log` in TS/JS — connectors/migrations/20231109_2_create_gdrive_c…
info TODO/FIXME marker in shipping code — connectors/src/api/configuration.ts:84
low Stray `console.log` in TS/JS — cli/dust-cli/tsup.config.ts:16
info TODO/FIXME marker in shipping code — front/types/api/internal/agent_configurati…

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/01cb7246-ff70-4ac6-af6b-2a731e91b79c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/01cb7246-ff70-4ac6-af6b-2a731e91b79c/

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.