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.

shepherdjerred/monorepo

https://github.com/shepherdjerred/monorepo · scanned 2026-06-16 00:13 UTC (2 months, 2 weeks ago)

1136 raw signals (0 security + 1136 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 998 actionable findings from 1 signal source. 138 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 · 998 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 12 High 54 Medium 248 Low 396 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 998 Crowd 0 Layer: Software 26 Frontend 332 Network 41 Hardware 18 Security 73 Cicd 5 Quality 423 Api 80

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

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 24 places
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `rs_legacy` in packages/birmel/tests/voltagent/memo…

View all legacy markers findings →

Commented-out code 209 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 scripts/check-todos.ts:52
info Commented-code block (8 lines) in scripts/validate-commit-msg.ts:26
info Commented-code block (6 lines) in scripts/scrape-apple-hig.py:2
info Commented-code block (5 lines) in scripts/bench.py:2
info Commented-code block (7 lines) in scripts/setup.ts:352
info Commented-code block (6 lines) in scripts/check-tunnel-dns-coverage.ts:151
info Commented-code block (5 lines) in scripts/observability/local-stack/emit-test-t…
info Commented-code block (5 lines) in scripts/ci/src/pipeline-builder.ts:113
info Commented-code block (7 lines) in scripts/ci/src/change-detection.ts:946
info Commented-code block (6 lines) in scripts/ci/src/__tests__/dagger-hygiene.test.…
info Commented-code block (5 lines) in scripts/ci/src/__tests__/buildkite.test.ts:5
info Commented-code block (6 lines) in scripts/ci/src/__tests__/pipeline-builder.tes…

View all commented-out code findings →

Config drift 39 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 Stray `console.log` in TS/JS — packages/eslint-config/src/rules/prefer-async-aw…
low Stray `console.log` in TS/JS — packages/eslint-config/src/rules/prefer-zod-vali…
low Stray `console.log` in TS/JS — packages/eslint-config/src/rules/prefer-structur…
low Stray `console.log` in TS/JS — packages/eslint-config/src/rules/satori-best-pra…
low Stray `console.log` in TS/JS — packages/eslint-config/src/rules/no-function-ove…
low Stray `console.log` in TS/JS — packages/eslint-config/src/rules/no-use-effect.t…
info TODO/FIXME marker in shipping code — packages/tasks-for-obsidian/eslint.config.…
medium Insecure pattern 'node_child_process' in packages/eslint-config/src/rules/share… packages/eslint-config/src/rules/shared/tool-runn…:10
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: packages/dotfiles/dot_agents/skil… packages/dotfiles/dot_agents/skills/dagger-helper…:237
high Agent instruction/config may expose a secret: packages/dotfiles/dot_agents/skil… packages/dotfiles/dot_agents/skills/tailscale-hel…:163
high Agent instruction/config may expose a secret: packages/dotfiles/dot_agents/skil… packages/dotfiles/dot_agents/skills/cdk8s-abstrac…:384

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/add84b34-dc9f-474d-8f7d-c726d5e4d859/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/add84b34-dc9f-474d-8f7d-c726d5e4d859/

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.