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.

texnottexas/landing-page

https://github.com/texnottexas/landing-page · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

49 raw signals (0 security + 49 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

66.7% cov · 46 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 29 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 46 Crowd 0 Layer: Frontend 2 Security 23 Cicd 2 Quality 19

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 `threats_legacy` in scripts/ssc-r14-planning.py:284
low Old/deprecated-named symbol `threats_legacy` in scripts/ssc-r125-planning.py:156

View all legacy markers findings →

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

8 matching findings on this repo

info Commented-code block (10 lines) in merge-bookmarklet.js:5
info Commented-code block (6 lines) in all-bookmarklet.js:47
info Commented-code block (14 lines) in dismantle-bookmarklet.js:6
info Commented-code block (5 lines) in feedback-widget.js:221
info Commented-code block (5 lines) in defense-skip-bookmarklet.js:10
info Commented-code block (5 lines) in scripts/ssc-r14-planning.py:106
info Commented-code block (8 lines) in scripts/ssc-r125-planning.py:80
info Commented-code block (10 lines) in scripts/ssc-r12-planning.py:352

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium CI is configured but no tests are detected

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/b53cab06-44da-450b-8c20-d14100b73011/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b53cab06-44da-450b-8c20-d14100b73011/

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.