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

raymdl/BF6-Weapon-Analyzer

https://github.com/raymdl/BF6-Weapon-Analyzer · scanned 2026-06-15 23:47 UTC (2 months, 3 weeks ago)

27 raw signals (0 security + 27 graph)

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

Complete repo analysis

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

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

Showing 23 of 27 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 — season-2/ui/app.js:14
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 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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in preview_bloom.html:674
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
preview_bloom.html:674 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in preview_distance.html:722
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
preview_distance.html:722 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in season-2/preview_bloom.html:661
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
season-2/preview_bloom.html:661 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in season-2/preview_distance.html:710
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
season-2/preview_distance.html:710 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in season-2/sim/loadout.js:137
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
season-2/sim/loadout.js:137 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in season-2/ui/app.js:184
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
season-2/ui/app.js:184 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sim/loadout.js:153
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sim/loadout.js:153 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/app.js:388
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/app.js:388 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in season-2/sim/loadout.js:264
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
season-2/sim/loadout.js:264 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in season-2/ui/app.js:242
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
season-2/ui/app.js:242 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in sim/loadout.js:310
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
sim/loadout.js:310 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in ui/app.js:31
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
ui/app.js:31 Insert adjacent html
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 11 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph security security conf 1.00 Insecure pattern 'document_write' in index.html:8
Found a known-risky pattern (document_write). Review and replace if possible.
index.html:8 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in season-2/index.html:8
Found a known-risky pattern (document_write). Review and replace if possible.
season-2/index.html:8 Document write
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 Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
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 quality Complexity conf 1.00 Very large file: season-2/ui/app.js (1295 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ui/app.js (1643 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/333960b0-f7d9-43c2-9a1b-365b480871a7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/333960b0-f7d9-43c2-9a1b-365b480871a7/

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.