BradGroux/veritas-kanban

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.

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

Scan timing: clone 8.93s · analysis 54.08s · 19.9 MB · GitHub API rate-limit (preflight)

https://github.com/BradGroux/veritas-kanban · scanned 2026-06-05 15:09 UTC (5 days, 2 hours ago) · 10 languages

626 raw signals (174 security + 452 graph) 30th percentile · Typescript · large (100-500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	43.1	0.25	10.78
`testing_score`	95.0	0.20	19.00
`documentation_score`	87.7	0.15	13.15
`practices_score`	85.0	0.15	12.75
`code_quality`	47.2	0.10	4.72
Overall		1.00	69.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 38 Medium 49 Low 148 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 78 System graph 220 Crowd 0 Layer: Quality 98 Security 8 Cicd 7 Software 66 Frontend 55 Network 6 Hardware 2 Api 56

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

low Old/deprecated-named symbol `hasLegacy` in server/src/__tests__/middleware/rate…
low Old/deprecated-named symbol `workspace_memberships_legacy` in server/src/storag…

View all legacy markers findings →

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

5 matching findings on this repo

info Commented-code block (6 lines) in web/src/hooks/useTasks.ts:177
info Commented-code block (6 lines) in server/src/index.ts:3
info Commented-code block (6 lines) in server/src/__tests__/storage/file-storage.tes…
info Commented-code block (10 lines) in server/src/routes/activity.ts:14
info Commented-code block (6 lines) in server/src/services/file-lock.ts:18

View all commented-out code findings →

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

10 matching findings on this repo

low File has no detected symbols: playwright.config.ts
low File has no detected symbols: eslint.config.js
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: mcp/vitest.config.ts
low File has no detected symbols: shared/src/types/config.types.ts
low File has no detected symbols: cli/vitest.config.ts
low File has no detected symbols: desktop/electron.vite.config.ts
low File has no detected symbols: desktop/vitest.config.ts
low Stray `console.log` in TS/JS — server/src/config/security.ts:439
medium `fetch()` without try/.catch or AbortSignal — web/src/lib/api/config.ts:15

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/52ffb460-31b3-4e4c-8fbc-f948099ce16c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/52ffb460-31b3-4e4c-8fbc-f948099ce16c/

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.