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 138 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

oven-sh/bun

https://github.com/oven-sh/bun · scanned 2026-06-05 06:54 UTC (6 days, 1 hour ago) · 10 languages

7454 raw signals (130 security + 7324 graph) 11/13 scanners ran 44th percentile · Typescript · large (100-500K LoC) System graph score 58 (higher by 15)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 6 days, 1 hour ago · v2 · 3668 actionable findings from 2 signal sources. 124 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 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 57.0 0.20 11.40
documentation_score 65.0 0.15 9.75
practices_score 65.0 0.15 9.75
code_quality 45.0 0.10 4.50
Overall 1.00 73.2
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 6 findings
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.
6 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 14 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 7 places
  • low Near-duplicate function bodies in 6 places repo-level
  • low Near-duplicate function bodies in 4 places repo-level
View all duplicates & near-duplicates findings →
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
  • low Stray `console.log` in TS/JS — test/js/node/test/fixtures/typescript/ts/transfo…
  • info Commented-code block (7 lines) in test/js/node/test/parallel/test-stream2-reada…
  • low Old/deprecated-named symbol `ToLegacy` in test/js/node/test/parallel/test-crypt…
  • low Old/deprecated-named symbol `unstable_legacy` in bench/react-hello-world/react-…
  • low Old/deprecated-named symbol `dgram_legacy` in src/js/node/dgram.ts:440
  • low Old/deprecated-named symbol `emitCloseLegacy` in src/js/internal/streams/destro…
View all legacy markers findings →
Commented-out code 1164 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 test/harness.ts:48
  • info Commented-code block (5 lines) in test/bundler/bundler_regressions.test.ts:5
  • info Commented-code block (5 lines) in test/bundler/bundler_naming.test.ts:305
  • info Commented-code block (5 lines) in test/bundler/bundler_cjs.test.ts:6
  • info Commented-code block (40 lines) in test/bundler/bundler_plugin.test.ts:700
  • info Commented-code block (5 lines) in test/bundler/bundler_compile.test.ts:8
  • info Commented-code block (6 lines) in test/bundler/bundler_edgecase.test.ts:1879
  • info Commented-code block (5 lines) in test/bundler/bundler_barrel.test.ts:579
  • info Commented-code block (8 lines) in test/bundler/bun-build-api.test.ts:321
  • info Commented-code block (5 lines) in test/bundler/bundler_minify.test.ts:1336
  • info Commented-code block (5 lines) in test/bundler/bun-build-compile.test.ts:446
  • info Commented-code block (7 lines) in test/bundler/bun-build-compile-wasm.test.ts:40
View all commented-out code findings →
Config drift 19 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
  • info TODO/FIXME marker in shipping code — test/bundler/esbuild/tsconfig.test.ts:233
  • low Stray `console.log` in TS/JS — test/bundler/esbuild/tsconfig.test.ts:16
  • info TODO/FIXME marker in shipping code — test/config/bunfig/preload.test.ts:42
  • low Stray `console.log` in TS/JS — test/config/bunfig/fixtures/preload/many/index.t…
  • low Stray `console.log` in TS/JS — test/internal/macos-cross-config.test.ts:250
  • low Stray `console.log` in TS/JS — test/js/node/test/parallel/test-process-config.j…
  • info TODO/FIXME marker in shipping code — test/js/bun/resolve/tsconfig-extends-leak.…
  • low Stray `console.log` in TS/JS — test/js/bun/resolve/tsconfig-extends-leak.test.t…
  • low Stray `console.log` in TS/JS — test/cli/run/tsconfig-override.test.ts:10
  • low Very large file: test/bundler/esbuild/tsconfig.test.ts (1957 lines)
  • low Very large file: src/runtime/server/ServerConfig.rs (1593 lines)
  • info Commented-code block (5 lines) in test/integration/vite-build/the-test-app/vite…
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/27aaf1dc-7325-46a0-9235-bbef12ce7b77/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/27aaf1dc-7325-46a0-9235-bbef12ce7b77/

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.