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.

quartermileclint/sagereasoning

https://github.com/quartermileclint/sagereasoning · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

445 raw signals (0 security + 445 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 427 actionable findings from 1 signal source. 18 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 427 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 9 Medium 83 Low 201 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 427 Crowd 0 Layer: Software 29 Frontend 145 Security 42 Cicd 2 Quality 209

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

2 matching findings on this repo

low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places repo-level

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 `resolvedLegacy` in website/src/lib/__tests__/journ…

View all legacy markers findings →

Commented-out code 125 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 (7 lines) in sage-mentor/persona.ts:119
info Commented-code block (5 lines) in sage-mentor/profile-store.ts:781
info Commented-code block (6 lines) in sage-mentor/support-agent.ts:54
info Commented-code block (6 lines) in sage-mentor/ring-wrapper.ts:144
info Commented-code block (5 lines) in sage-mentor/proactive-scheduler.ts:431
info Commented-code block (11 lines) in trust-layer/types/accreditation.ts:126
info Commented-code block (5 lines) in archive/2026-04-21_inline-backups/ops-continu…
info Commented-code block (5 lines) in archive/2026-04-22_inline-backups/ops-continu…
info Commented-code block (10 lines) in operations/migrations/2026-05-03-corpus-pass…
info Commented-code block (9 lines) in operations/migrations/2026-05-04-corpus-passa…
info Commented-code block (10 lines) in operations/migrations/2026-05-03-d-a16-catal…
info Commented-code block (7 lines) in scripts/mentor-ring-proof-verification.mjs:147

View all commented-out code findings →

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

11 matching findings on this repo

low Stray `console.log` in TS/JS — website/src/app/api/__tests__/r20a-configuration…
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/SKILL.md:191
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/php/managed-a…:433
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/ruby/managed-…:309
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/shared/model-…:614
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/csharp/claude…:21
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/python/claude…:114
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/java/claude-a…:20
high Agent instruction/config may expose a secret: .claude/skills/anthropic/claude-a… .claude/skills/anthropic/claude-api/go/managed-ag…:452
info Commented-code block (6 lines) in website/src/app/api/__tests__/r20a-configurat…

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/b04dd47a-aa85-4a6b-a98f-020b81b7f690/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b04dd47a-aa85-4a6b-a98f-020b81b7f690/

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.