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.

shaun0927/Ouroforge

https://github.com/shaun0927/Ouroforge · scanned 2026-06-16 00:10 UTC (2 months, 2 weeks ago)

199 raw signals (0 security + 199 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 90.0/100 with 88.9% coverage. It contains 8856 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 199 findings — concentrated in security (97), quality (84), frontend (7). Risk profile is high: 0 critical, 43 high, 74 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 110 of 189 actionable findings. 199 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.

high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/export_profile.rs:282
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/export_profile.rs:282 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/export_verification.rs:266
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/export_verification.rs:266 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/performance_soak.rs:497
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/performance_soak.rs:497 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/plugin_evidence.rs:709
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/plugin_evidence.rs:709 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/plugin_manifest.rs:646
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/plugin_manifest.rs:646 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/production_handoff.rs:503
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/production_handoff.rs:503 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/production_qa_m158.rs:681
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/production_qa_m158.rs:681 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/production_qa_matrix.rs:797
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/production_qa_matrix.rs:797 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/production_qa_verdict.rs:462
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/production_qa_verdict.rs:462 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/production_review_gates.rs:493
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/production_review_gates.rs:493 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/production_roles.rs:602
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/production_roles.rs:602 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_error_classifier.rs:453
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_error_classifier.rs:453 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_evidence_bundle.rs:391
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_evidence_bundle.rs:391 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_failure_backlog.rs:424
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_failure_backlog.rs:424 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_flake_rerun_policy.rs:435
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_flake_rerun_policy.rs:435 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_performance_budget.rs:582
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_performance_budget.rs:582 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_regression_coverage.rs:245
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_regression_coverage.rs:245 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/qa_run_matrix.rs:458
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/qa_run_matrix.rs:458 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/safe_source_apply_demo.rs:576
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/safe_source_apply_demo.rs:576 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/team_production_collaboration.rs:972
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/team_production_collaboration.rs:972 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-core/src/visual_regression_scale.rs:472
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-core/src/visual_regression_scale.rs:472 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-evaluator/src/lib.rs:2519
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-evaluator/src/lib.rs:2519 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_asset_placeholder_plan.rs:556
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_asset_placeholder_plan.rs:556 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_design_brief.rs:572
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_design_brief.rs:572 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_feasibility_gate.rs:572
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_feasibility_gate.rs:572 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_gameplay_behavior_plan.rs:755
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_gameplay_behavior_plan.rs:755 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_mechanics_mapping.rs:771
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_mechanics_mapping.rs:771 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_project_scaffold_plan.rs:393
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_project_scaffold_plan.rs:393 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_prototype_apply.rs:680
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_prototype_apply.rs:680 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_prototype_draft_bundle.rs:507
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_prototype_draft_bundle.rs:507 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_prototype_evidence.rs:660
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_prototype_evidence.rs:660 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_prototype_evidence_bundle.rs:633
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_prototype_evidence_bundle.rs:633 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_prototype_task_graph.rs:501
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_prototype_task_graph.rs:501 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_requirement_extraction.rs:513
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_requirement_extraction.rs:513 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_scenario_acceptance_plan.rs:585
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_scenario_acceptance_plan.rs:585 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-gdd/src/gdd_scene_level_plan.rs:719
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-gdd/src/gdd_scene_level_plan.rs:719 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-source-apply/src/source_apply_diagnosis_patch_integration.rs:353
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-source-apply/src/source_apply_diagnosis_patch_integration.rs:353 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-source-apply/src/source_apply_review_enforcement.rs:379
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-source-apply/src/source_apply_review_enforcement.rs:379 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-source-apply/src/source_apply_rollback_snapshot.rs:303
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-source-apply/src/source_apply_rollback_snapshot.rs:303 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-source-apply/src/source_apply_sandbox_promotion.rs:361
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-source-apply/src/source_apply_sandbox_promotion.rs:361 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/ouroforge-source-apply/src/source_apply_transaction_hardening.rs:542
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/ouroforge-source-apply/src/source_apply_transaction_hardening.rs:542 Eval used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — examples/authoring-cockpit/ap-authoring-evidence.js:9
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 — examples/authoring-cockpit/at-safe-apply-evidence.js:3
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 — examples/authoring-cockpit/cockpit.js:6014
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 — examples/authoring-cockpit/editor-draft-panel.test.cjs:138
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 — examples/authoring-cockpit/editor-triad.js:266
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 — scripts/m170-7-multi-level-product-observed-audit.test.cjs:119
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 — scripts/m173-7-qa-balance-loop-product-observed-campaign-live.test.cjs:94
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 — scripts/m176-6-rc-package-product-observed-smoke.test.cjs:68
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 — scripts/m189-reference-game-dogfood-presentation-assets.test.cjs:87
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 — tools/asset-ingest-audit/audit.mjs:364
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 — tools/balance-cycle-audit/audit.mjs:272
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 — tools/dogfood-cycle-audit/audit.mjs:437
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 — tools/editor-triad-audit/audit.mjs:357
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 — tools/game3-playable-audit/audit.mjs:199
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 — tools/live-observability-runner/runner.mjs:120
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 — tools/preview-loop-audit/audit.mjs:309
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 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 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 34, 37
.github/workflows/cross-platform-digest.yml:34, 37 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in ci/sim-parity-check.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
ci/sim-parity-check.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/era-ae-browser-verified-gate.cjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/era-ae-browser-verified-gate.cjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/game6-local-rc-package-smoke.cjs:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/game6-local-rc-package-smoke.cjs:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m147-local-telemetry-cdp-audit.cjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m147-local-telemetry-cdp-audit.cjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m147-telemetry-viewer-live-audit.cjs:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m147-telemetry-viewer-live-audit.cjs:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m165-era-aa-closure-comments-audit.cjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m165-era-aa-closure-comments-audit.cjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m165-final-readiness-audit.cjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m165-final-readiness-audit.cjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m165-generated-state-audit.cjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m165-generated-state-audit.cjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m165-graphql-readiness-audit.cjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m165-graphql-readiness-audit.cjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m165-prerequisite-pr-stack-audit.cjs:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m165-prerequisite-pr-stack-audit.cjs:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/m165-prerequisite-readiness-audit.cjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/m165-prerequisite-readiness-audit.cjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/validate-era-aa-origin-main-capability-inventory.cjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/validate-era-aa-origin-main-capability-inventory.cjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/asset-ingest-audit/audit.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/asset-ingest-audit/audit.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/balance-cycle-audit/audit.mjs:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/balance-cycle-audit/audit.mjs:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/dogfood-cycle-audit/audit.mjs:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/dogfood-cycle-audit/audit.mjs:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/editor-triad-audit/audit.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/editor-triad-audit/audit.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/game3-playable-audit/audit.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/game3-playable-audit/audit.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/live-observability-runner/runner.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/live-observability-runner/runner.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/preview-loop-audit/audit.mjs:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/preview-loop-audit/audit.mjs:20 Node child process
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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 147 placeholder/mock markers across 25 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 533 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 31, 66, 78, 84
.github/workflows/cross-platform-digest.yml:31, 66, 78, 84 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/era_aq_browser_validate.py:wait_json, scripts/era_at_browser_validate.py:wait_json 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.
4 occurrences
repo-level (4 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/era_aq_browser_validate.py:reader, scripts/era_ap_browser_validate.py:reader, scripts/era_at_browser_validate.py:reader This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consoli…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `gameplay_logic_demo_v1` in examples/gameplay-logic-demo-v1/schema-smoke.test.cjs:19
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 4 occurrences Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
scripts/era_ao_aw_browser_validate.py:52
scripts/era_ap_browser_validate.py:53
scripts/era_aq_browser_validate.py:10
scripts/era_at_browser_validate.py:8
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 — ci/sim-parity-check.js:54
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 — examples/era-am-tiny-game/game.js:40
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 — examples/era-an-small-game/game.js:43
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 — examples/game-runtime/check_budget_ceiling.js:56
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 — examples/game-runtime/evidence_boundary_check.js:54
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 — examples/game-runtime/visual_gate_hash_check.js:35
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 Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — scripts/era_ao_aw_browser_validate.py:52
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-cli/src/main.rs (4234 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-cli/tests/artifact_commands.rs (4942 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/src/behavior_runtime.rs (2377 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/src/card_roguelite_substrate.rs (1573 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/src/lib.rs (14026 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/tests/behavior_contracts.rs (1341 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/tests/evolve_contracts.rs (1890 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/tests/export_contracts.rs (1455 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/tests/gdd_contracts.rs (1917 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-core/tests/plugin_contracts.rs (1484 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ouroforge-evaluator/src/lib.rs (2966 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/authoring-cockpit/cockpit.js (7065 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/authoring-cockpit/cockpit.test.cjs (4488 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/evidence-dashboard/dashboard.js (3524 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/evidence-dashboard/dashboard.test.cjs (2667 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: examples/game-runtime/runtime.js (4815 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/01faa7af-1bb6-4a01-a380-3610f43cd797/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/01faa7af-1bb6-4a01-a380-3610f43cd797/

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.