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

yuyanishimura0312/miratuku-news-v2

https://github.com/yuyanishimura0312/miratuku-news-v2 · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

155 raw signals (0 security + 155 graph)

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

Complete repo analysis

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

JSON
Combined
62.3
/100
Security checks
62
0 findings
System graph
62
88.9% cov · 124 findings
Critical
3
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 3 High 0 Medium 87 Low 33 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 124 Crowd 0 Layer: Software 16 Frontend 1 Security 59 Cicd 2 Quality 46
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 62.3/100 with 88.9% coverage. It contains 3694 nodes across 13 cross-layer flows, written primarily in mixed languages. Engine surfaced 155 findings — concentrated in quality (61), security (59), software (29). Risk profile is high: 3 critical, 0 high, 87 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 123 of 124 actionable findings. 155 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.

critical System graph security Secrets conf 1.00 Possible secret in admin/index.html
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
admin/index.html:804
critical System graph security Secrets conf 1.00 Possible secret in js/shared/firebase-config.js
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
js/shared/firebase-config.js:3
critical System graph security Secrets conf 1.00 Possible secret in js/shared/i18n.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
js/shared/i18n.js:134
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — js/pages/analysis-reports.js:115
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 — js/pages/cla.js:453
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 — js/shared/data-cache.js:91
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 — js/shared/data-loader.js:7
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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
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 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/deploy.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboards/seo-execution.html:6663
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboards/seo-execution.html:6663 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin/index.html:814
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin/index.html:814 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in answer.html:1523
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
answer.html:1523 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in book/tech-acceleration/chapters/appendix-c.html:230
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
book/tech-acceleration/chapters/appendix-c.html:230 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/ak-explorer.html:239
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/ak-explorer.html:239 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/an-phylogeny.html:124
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/an-phylogeny.html:124 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/an.html:3673
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/an.html:3673 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/cla-integrated.html:684
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/cla-integrated.html:684 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/cla-timeline.html:281
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/cla-timeline.html:281 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/cla.html:459
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/cla.html:459 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/fk.html:114
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/fk.html:114 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/ic.html:675
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/ic.html:675 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/it.html:183
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/it.html:183 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/mg.html:177
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/mg.html:177 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/mt.html:293
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/mt.html:293 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/my-canada-indigenous.html:99
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/my-canada-indigenous.html:99 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/my-okinawa.html:133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/my-okinawa.html:133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/my.html:165
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/my.html:165 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/pd.html:599
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/pd.html:599 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/placeness-map.html:352
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/placeness-map.html:352 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/pt.html:190
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/pt.html:190 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/su.html:153
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/su.html:153 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/tech-phylogenetics.html:313
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/tech-phylogenetics.html:313 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/timeline-events.html:2180
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/timeline-events.html:2180 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/tk-canada.html:217
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/tk-canada.html:217 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/tk-map.html:191
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/tk-map.html:191 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/tk-okinawa.html:167
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/tk-okinawa.html:167 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/tk.html:103
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/tk.html:103 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/transformation-unified.html:846
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/transformation-unified.html:846 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/upr.html:224
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/upr.html:224 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/wiki-planner.html:164
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/wiki-planner.html:164 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboards/yk.html:208
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboards/yk.html:208 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in databases.html:1329
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
databases.html:1329 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in db-planner.html:380
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
db-planner.html:380 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in forum/esse-sense-co-creation-2026-06-03-k9m4x/edit/index.html:308
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
forum/esse-sense-co-creation-2026-06-03-k9m4x/edit/index.html:308 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in integrated-monetization-textbook.html:3835
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
integrated-monetization-textbook.html:3835 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in integrated.html:296
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
integrated.html:296 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/foresight.js:114
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/foresight.js:114 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/analysis-reports.js:15
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/analysis-reports.js:15 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/cla.js:16
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/cla.js:16 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/databases.js:18
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/databases.js:18 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/foresight.js:43
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/foresight.js:43 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/guide.js:58
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/guide.js:58 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/home.js:70
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/home.js:70 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/media.js:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/media.js:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/papers.js:13
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/papers.js:13 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/reports.js:33
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/reports.js:33 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/signals.js:14
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/signals.js:14 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/themes.js:100
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/themes.js:100 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/pages/user-reports.js:11
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/pages/user-reports.js:11 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/shared/article-modal.js:290
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/shared/article-modal.js:290 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/shared/auth-guard.js:33
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/shared/auth-guard.js:33 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/shared/nav.js:58
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/shared/nav.js:58 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in js/shared/ui-components.js:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
js/shared/ui-components.js:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reports/domain-growth-analysis.html:464
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reports/domain-growth-analysis.html:464 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in admin/index.html:850
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
admin/index.html:850 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/data-driven-foresight/_deploy.py:19
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/data-driven-foresight/_deploy_assets.py:13
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/reports-public/foodag-2030-2100/_deploy.py:28
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/reports-public/manufacturing-orchestra/_deploy.py:24
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/reports-public/mobility-2030-2100/_deploy.py:24
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/ryoiki/phase-e/_deploy_8questions.py:19
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/ryoiki/phase-e/_deploy_futures.py:18
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/ryoiki/phase-e/_deploy_futures_series_v2.py:19
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/ryoiki/phase-e/_deploy_methodology.py:19
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — dashboards/ryoiki/phase-e/_deploy_to_journal.py:19
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — reports/_repo-system/build_report.py:665
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_classify_typology.py:14
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage1_definition.py:26
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage2_ontological_framework.py:27
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage3_behavioral_enrichment.py:33
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage4_coverage_audit.py:35
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage5_ontological_role.py:33
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage7_parallel.py:51
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage7_personality_reanalysis.py:34
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage8_gta.py:34
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/yokai_stage8_parallel_open.py:36
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 120 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 832 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 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 25, 27, 29, 34
.github/workflows/deploy.yml:25, 27, 29, 34 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: scripts/yokai_stage8_parallel_open.py:get_api_key, scripts/yokai_stage7_personality_reanalysis.py:get_api_key, scripts/yokai_stage5_ontological_role.py:get_api_key, scripts/yokai_stage7_parallel.py:get_api_key This is *the* AI-coder failure mode (4× …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 11 places
Functions with the same first-5-line body hash: dashboards/ryoiki/phase-e/_deploy_to_journal.py:get_password, dashboards/ryoiki/phase-e/_deploy_8questions.py:get_password, dashboards/ryoiki/phase-e/_deploy_futures_series_v2.py:get_password, dashboards/ryoiki/phase-e/_deploy_futures.py:get_password …
duplicatesduplication
low System graph quality Integrity conf 1.00 15 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/extract_system_patterns.py:hierarchical_cluster, scripts/extract_system_patterns.py:h 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 separ…
15 occurrences
repo-level (15 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/yokai_stage7_personality_reanalysis.py:main, scripts/yokai_stage5_ontological_role.py:main, scripts/yokai_stage3_behavioral_enrichment.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: dashboards/ryoiki/phase-e/_deploy_to_journal.py:main, dashboards/ryoiki/phase-e/_deploy_8questions.py:main, dashboards/ryoiki/phase-e/_deploy_methodology.py:main, dashboards/data-driven-foresight/_deploy.py:main This is *the* AI-coder failure mode (4…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `analyses_v2` in scripts/generate_dashboards.py:26
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 `cla_v2` in js/pages/cla.js:716
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 `expand_brief_v2` in dashboards/ryoiki/phase-e/futures-series/_build/build_expand_batch_v2.py:12
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 `expand_brief_v2` in dashboards/ryoiki/phase-e/futures-series/_build/build_short_batches.py:12
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 software Dead code conf 1.00 Possibly dead Python function: convert_year
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/ryoiki/phase-e/_convert_numerals.py:18
low System graph software Dead code conf 1.00 Possibly dead Python function: decade_from_date
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/crossref_patterns_news.py:143
low System graph software Dead code conf 1.00 Possibly dead Python function: deduplicate_concepts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_mg_database.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_evidence
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_cla_deep_data.py:98
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_myth_mapping
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_cla_deep_data.py:146
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_ngram_overlay
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_cla_deep_data.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_signal_network
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_cla_deep_data.py:61
low System graph software Dead code conf 1.00 Possibly dead Python function: prose_arts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/_gen_ak_section.py:192
low System graph software Dead code conf 1.00 Possibly dead Python function: prose_engineering
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/_gen_ak_section.py:161
low System graph software Dead code conf 1.00 Possibly dead Python function: prose_humanities
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/_gen_ak_section.py:69
low System graph software Dead code conf 1.00 Possibly dead Python function: prose_natural
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/_gen_ak_section.py:130
low System graph software Dead code conf 1.00 Possibly dead Python function: prose_social
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/_gen_ak_section.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: render_lens_body
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dashboards/ryoiki/phase-e/futures-series/_build/render.py:156
low System graph software Dead code conf 1.00 14 occurrences Possibly dead Python function: run_codex
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
12 files, 12 locations
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_full.py:58
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupB.py:67
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupC.py:69
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupD.py:69
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupE.py:78
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupE_v2.py:81
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupF.py:70
dashboards/ryoiki/phase-e/codex_tasks/_orchestrate_codex_groupF_v2.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/generate_cla_text.py:193
low System graph software Dead code conf 1.00 Possibly dead Python function: svg_block_sub
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/dkb-v2/recolor_svgs.py:121
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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 — js/pages/cla.js:450
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: js/pages/cla.js (1214 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/analyze_sif.py (1616 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/48f53bf2-f021-4175-a2e9-3e6190f15cb5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/48f53bf2-f021-4175-a2e9-3e6190f15cb5/

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.