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.
Sign up free Scan another repo

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
Combined
77.1
/100
Security checks
77
0 findings
System graph
77
66.7% cov · 46 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
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
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 77.1/100 with 66.7% coverage. It contains 327 nodes across 10 cross-layer flows, written primarily in mixed languages. Engine surfaced 49 findings — concentrated in security (23), quality (19), cicd (5). Risk profile is low: 0 critical, 0 high, 32 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 37 of 46 actionable findings. 49 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — feedback-widget.js:265
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — seal-stone-train.js:80
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
4 files, 4 locations
.github/workflows/calendar-snapshot.yml
.github/workflows/pages.yml
.github/workflows/titan-snapshot.yml
.github/workflows/train-backup.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/bases.html:556
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/bases.html:556 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/battle-replay.html:1017
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/battle-replay.html:1017 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/battle-report.html:4447
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/battle-report.html:4447 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/decor-index.html:1349
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/decor-index.html:1349 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/easter-wishing.html:256
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/easter-wishing.html:256 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/heroes-awakening.html:2859
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/heroes-awakening.html:2859 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/heroes.html:489
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/heroes.html:489 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/ht-chips.html:454
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/ht-chips.html:454 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/index.html:6517
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/index.html:6517 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/matchup-participation.html:326
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/matchup-participation.html:326 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/roadmap.html:263
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/roadmap.html:263 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/ssc-map.html:2312
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/ssc-map.html:2312 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/ssc-merit-report.html:702
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/ssc-merit-report.html:702 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/storm-battle-plan.html:589
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/storm-battle-plan.html:589 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/storm-briefing.html:440
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/storm-briefing.html:440 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/storm-duel-selection.html:1133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/storm-duel-selection.html:1133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/tex-armory.html:622
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/tex-armory.html:622 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/titan-admin.html:991
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/titan-admin.html:991 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/titan-battle-plan.html:317
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/titan-battle-plan.html:317 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/titan-roster.html:860
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/titan-roster.html:860 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/titan-signup.html:276
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/titan-signup.html:276 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in pages/treasury.html:584
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
pages/treasury.html:584 Direct innerhtml assignment
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 16 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 97 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/pages.yml:56 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `threats_legacy` in scripts/ssc-r125-planning.py:156
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `threats_legacy` in scripts/ssc-r14-planning.py:284
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/ud-distribute-r5.js:138
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/ud-distribute-r6.js:94
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: all-bookmarklet.js (1840 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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.