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.

vinceblank/agent-tempo

https://github.com/vinceblank/agent-tempo · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

346 raw signals (0 security + 346 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 320 actionable findings from 1 signal source. 26 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 · 320 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 10 Medium 44 Low 47 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 320 Crowd 0 Layer: Frontend 28 Hardware 5 Security 34 Cicd 3 Quality 245 Api 5

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.

Legacy markers 2 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.

2 matching findings on this repo

info Commented-code block (6 lines) in tests/cli/legacy-migration.test.ts:157
low Old/deprecated-named symbol `dstLegacy` in src/cli/daemon-command.ts:421

View all legacy markers findings →

Commented-out code 212 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 (5 lines) in tests/adapters/claude-code-headless/prompt.te…
info Commented-code block (5 lines) in tests/adapters/claude-code-headless/registry.…
info Commented-code block (6 lines) in tests/adapters/mock/recruit-gate.test.ts:43
info Commented-code block (5 lines) in tests/adapters/mock/build-exclusion.test.ts:77
info Commented-code block (5 lines) in tests/client/ensemble-verbs.test.ts:303
info Commented-code block (5 lines) in tests/client/list-ensembles.test.ts:109
info Commented-code block (6 lines) in tests/pi/install.test.ts:208
info Commented-code block (5 lines) in tests/tui/status-bar.test.ts:326
info Commented-code block (5 lines) in tests/tui/conversation-stream-directed.test.t…
info Commented-code block (7 lines) in tests/tui/sse-handler.test.ts:176
info Commented-code block (5 lines) in tests/tui/palette.test.ts:211
info Commented-code block (5 lines) in tests/tui/conversation-stream-broadcast.test.…

View all commented-out code findings →

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

7 matching findings on this repo

low Stray `console.log` in TS/JS — src/cli/config-command.ts:116
info Commented-code block (7 lines) in dashboard/vite.config.ts:8
info Commented-code block (5 lines) in dashboard/eslint.config.js:40
info Commented-code block (5 lines) in dashboard/vitest.config.ts:5
info Commented-code block (13 lines) in dashboard/tests-overflow/playwright.config.t…
info Commented-code block (10 lines) in src/config.ts:835
info Commented-code block (5 lines) in src/cli/config-command.ts:29

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/a0522150-cf23-44d5-a541-8f841c9b04b1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a0522150-cf23-44d5-a541-8f841c9b04b1/

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.