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

codescooper/AwemA-Games

https://github.com/codescooper/AwemA-Games · scanned 2026-06-17 01:50 UTC (1 month, 1 week ago)

24 raw signals (0 security + 24 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -28.9 (diff) · 24 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 24 of 24 actionable findings. 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 'new_function_used' in engine/atelier.html:309
Found a known-risky pattern (new_function_used). Review and replace if possible.
engine/atelier.html:309 New function used
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
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, ci, lockfile. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, lockfile. 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 engine/atelier.html:323
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/atelier.html:323 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/awale-royal.html:301
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/awale-royal.html:301 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/banco.html:292
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/banco.html:292 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/cinema.html:111
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/cinema.html:111 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/classements.html:176
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/classements.html:176 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/conseil.html:204
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/conseil.html:204 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/echecs.html:332
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/echecs.html:332 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/harmattan.html:159
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/harmattan.html:159 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/idees.html:125
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/idees.html:125 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/monde.html:183
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/monde.html:183 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/prototype.html:217
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/prototype.html:217 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/sables.html:1808
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/sables.html:1808 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/salon.html:216
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/salon.html:216 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in engine/tamtam.html:188
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
engine/tamtam.html:188 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in engine/classements.html:192
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
engine/classements.html:192 Insert adjacent html
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
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 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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
package.json LockfileReproducibilityGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — engine/prototype.ts:339
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
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/efa270f8-6bb8-4d40-b7b8-a3aa4e7f9116/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/efa270f8-6bb8-4d40-b7b8-a3aa4e7f9116/

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.