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

richardjlyon/subsidy-clock

https://github.com/richardjlyon/subsidy-clock · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

45 raw signals (0 security + 45 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
85.8
/100
Security checks
86
0 findings
System graph
86
66.7% cov · 45 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 33 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 45 Crowd 0 Layer: Software 4 Network 22 Frontend 1 Security 7 Cicd 2 Quality 9
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 85.8/100 with 66.7% coverage. It contains 574 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 45 findings — concentrated in network (22), quality (9), security (7). Risk profile is low: 0 critical, 0 high, 33 medium. Recommended next step: open the network layer findings first — that's where the highest-impact wins live.

Showing 41 of 45 actionable findings. 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 — site/app.js:734
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 — site/explainers/common.js:38
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 — site/share.js:264
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 cicd CI/CD security conf 1.00 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.
.github/workflows/update.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/app.js:136
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/app.js:136 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/corrections.html:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/corrections.html:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/explainers/explainer.js:40
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/explainers/explainer.js:40 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/methodology.html:304
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/methodology.html:304 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/share.html:107
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/share.html:107 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in site/share.js:210
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
site/share.js:210 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 network Security conf 1.00 Privileged port 106 in use
Port 106 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 107 in use
Port 107 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 108 in use
Port 108 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 111 in use
Port 111 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 120 in use
Port 120 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 128 in use
Port 128 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 132 in use
Port 132 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 138 in use
Port 138 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/update.yml Ports
medium System graph network Security conf 1.00 Privileged port 75 in use
Port 75 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 76 in use
Port 76 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 77 in use
Port 77 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 79 in use
Port 79 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 81 in use
Port 81 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 83 in use
Port 83 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 86 in use
Port 86 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 87 in use
Port 87 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 90 in use
Port 90 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 93 in use
Port 93 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 96 in use
Port 96 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 98 in use
Port 98 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
medium System graph network Security conf 1.00 Privileged port 99 in use
Port 99 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
reference/deflators.yaml Ports
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 7 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/cache@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/update.yml:28 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/subsidy_engine/sitedata.py:write_corrections, src/subsidy_engine/sitedata.py:write This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_backfill_constraints
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/subsidy_engine/__main__.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_build_cards
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/subsidy_engine/__main__.py:148
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_build_site
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/subsidy_engine/__main__.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_update
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/subsidy_engine/__main__.py:24
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
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/d33733b4-d200-45e4-a370-e927720b41ad/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d33733b4-d200-45e4-a370-e927720b41ad/

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.