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.

Rahulsanecdote/AICalorietrackermain

https://github.com/Rahulsanecdote/AICalorietrackermain · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

177 raw signals (0 security + 177 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 20 Medium 36 Low 63 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 165 Crowd 0 Layer: Frontend 43 Hardware 4 Security 21 Cicd 1 Quality 74 Api 22

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

5 matching findings on this repo

low Stray `console.log` in TS/JS — archive/frontend-legacy/src/App.js:13
low Stray `console.log` in TS/JS — archive/frontend-legacy/plugins/health-check/hea…
low Stray `console.log` in TS/JS — archive/frontend-legacy/plugins/visual-edits/dev…
medium Insecure pattern 'node_child_process' in archive/frontend-legacy/plugins/visual… archive/frontend-legacy/plugins/visual-edits/dev-…:6
low Node manifest has dependencies but no lockfile: archive/frontend-legacy/package… archive/frontend-legacy/package.json

View all legacy markers findings →

Commented-out code 21 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 api/_billing/webhook.js:267
info Commented-code block (6 lines) in api/_lib/food-intelligence.js:192
info Commented-code block (5 lines) in api/_lib/notification-pipeline.js:12
info Commented-code block (5 lines) in api/_lib/adaptive-fractions.js:104
info Commented-code block (7 lines) in api/_lib/ingredient-aliases.js:2
info Commented-code block (5 lines) in api/_lib/recipes/candidate-search.js:410
info Commented-code block (5 lines) in api/_meals/create-from-recognition.js:89
info Commented-code block (5 lines) in api/_meals/create-from-recognition.test.js:96
info Commented-code block (6 lines) in api/_food/coffee-build.js:63
info Commented-code block (6 lines) in api/_food/coffee-build.test.js:4
info Commented-code block (5 lines) in api/_integrations/google-fit/exchange.js:52
info Commented-code block (6 lines) in scripts/reconcile-macros.mjs:2

View all commented-out code findings →

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

3 matching findings on this repo

medium Insecure pattern 'node_child_process' in scripts/verify-legal-policy-config.tes… scripts/verify-legal-policy-config.test.mjs:2
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .github/instructions/taskmaster.i… .github/instructions/taskmaster.instructions.md:377

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/70c844a7-532e-46de-9557-bb3b76ad907c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/70c844a7-532e-46de-9557-bb3b76ad907c/

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.