braintrustdata/braintrust-proxy

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.

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

Scan timing: clone 3.56s · analysis 32.75s · 5.6 MB · GitHub preflight 459ms

https://github.com/braintrustdata/braintrust-proxy · scanned 2026-06-05 19:27 UTC (1 week, 2 days ago) · 10 languages

228 raw signals (80 security + 148 graph) 58th percentile · Typescript · medium (20-100K LoC) System graph score 82 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 133 actionable findings from 2 signal sources. 21 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 · 74 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	43.9	0.25	10.97
`testing_score`	85.0	0.20	17.00
`documentation_score`	59.7	0.15	8.96
`practices_score`	89.0	0.15	13.35
`code_quality`	67.2	0.10	6.72
Overall		1.00	68.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 31 Medium 15 Low 59 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 59 System graph 74 Crowd 0 Layer: Quality 40 Security 7 Software 59 Cicd 4 Frontend 20 Network 1 Api 2

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.

Commented-out code 3 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/`.

3 matching findings on this repo

info Commented-code block (6 lines) in packages/proxy/scripts/sync_models.ts:31
info Commented-code block (10 lines) in packages/proxy/utils/tempCredentials.test.ts…
info Commented-code block (6 lines) in packages/proxy/schema/openai-realtime.ts:3

View all commented-out code findings →

Config drift 8 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.

8 matching findings on this repo

low File has no detected symbols: vitest.config.js
low File has no detected symbols: packages/proxy/vitest.config.js
low File has no detected symbols: packages/proxy/tsup.config.ts
low File has no detected symbols: apis/cloudflare/worker-configuration.d.ts
low File has no detected symbols: apis/cloudflare/tsup.config.ts
low File has no detected symbols: apis/vercel/tailwind.config.js
low File has no detected symbols: apis/vercel/next.config.js
low File has no detected symbols: apis/vercel/postcss.config.js

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/5b431bf3-77c6-490a-ab4d-1f966b8ba37c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5b431bf3-77c6-490a-ab4d-1f966b8ba37c/

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.