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.

averagejoematt/life-platform

https://github.com/averagejoematt/life-platform · scanned 2026-06-17 01:38 UTC (1 month, 2 weeks ago)

326 raw signals (0 security + 326 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -24.3 (diff) · 311 actionable findings from 1 signal source. 15 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 311 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 119 Low 118 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 311 Crowd 0 Layer: Software 28 Network 19 Security 64 Cicd 2 Quality 198

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

7 matching findings on this repo

low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 8 places repo-level
low Near-duplicate function bodies in 14 places
low Near-duplicate function bodies in 5 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/index.html:883 site/legacy/index.html:883
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/chronicle/index.h… site/legacy/chronicle/index.html:271
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/chronicle/archive… site/legacy/chronicle/archive/index.html:264
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/experiments/index… site/legacy/experiments/index.html:1054
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/experiments/detai… site/legacy/experiments/detail/index.html:243
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/supplements/index… site/legacy/supplements/index.html:729
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/training/index.ht… site/legacy/training/index.html:655
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/field-notes/index… site/legacy/field-notes/index.html:252
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/glucose/index.htm… site/legacy/glucose/index.html:567
medium Insecure pattern 'insert_adjacent_html' in site/legacy/glucose/index.html:583 site/legacy/glucose/index.html:583
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/biology/index.htm… site/legacy/biology/index.html:166
medium Insecure pattern 'direct_innerhtml_assignment' in site/legacy/labs/index.html:7… site/legacy/labs/index.html:781

View all legacy markers findings →

Commented-out code 71 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 tests/test_shared_modules.py:706
info Commented-code block (7 lines) in tests/test_integration_aws.py:148
info Commented-code block (6 lines) in tests/test_habitify_status_resolution.py:19
info Commented-code block (13 lines) in tests/test_iam_secrets_consistency.py:201
info Commented-code block (5 lines) in archive/20260308/deploy/patch_daily_brief_har…
info Commented-code block (6 lines) in archive/20260309/deploy/generate_maint1_requi…
info Commented-code block (5 lines) in cdk/stacks/mcp_stack.py:55
info Commented-code block (5 lines) in cdk/stacks/lambda_helpers.py:83
info Commented-code block (6 lines) in cdk/stacks/compute_stack.py:56
info Commented-code block (6 lines) in cdk/stacks/web_stack.py:97
info Commented-code block (6 lines) in cdk/stacks/role_policies.py:24
info Commented-code block (5 lines) in cdk/stacks/constants.py:49

View all commented-out code 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/b38df384-c9c0-414d-bd49-e453fc3d253f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b38df384-c9c0-414d-bd49-e453fc3d253f/

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.