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

shoyammishra/slay-the-spire-bench

https://github.com/shoyammishra/slay-the-spire-bench · scanned 2026-06-16 00:11 UTC (2 months, 2 weeks ago)

50 raw signals (0 security + 50 graph)

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

Complete repo analysis

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

JSON
Combined
86.9
/100
Security checks
87
0 findings
System graph
87
77.8% cov · 42 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 2 Medium 5 Low 26 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 42 Crowd 0 Layer: Software 5 Api 1 Frontend 1 Security 3 Cicd 1 Quality 31
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 86.9/100 with 77.8% coverage. It contains 894 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 50 findings — concentrated in quality (39), software (5), security (3). Risk profile is high: 0 critical, 2 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 33 of 42 actionable findings. 50 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 Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:6 SecretsClaude instruction
high System graph security security conf 1.00 Insecure pattern 'eval_used' in run_benchmark.py:134
Found a known-risky pattern (eval_used). Review and replace if possible.
run_benchmark.py:134 Eval used
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 ci. 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 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 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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 22 placeholder/mock markers across 6 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 42 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 Tests conf 1.00 Low test-to-source ratio
3 tests / 24 src (ratio 0.12).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: slay_bench/relics.py:on_combat_start, slay_bench/relics.py:on_combat_start, slay_bench/relics.py:on_combat_start, slay_bench/relics.py:on_combat_start 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 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: slay_bench/enemies_act2.py:on_death, slay_bench/enemies_act2.py:on_death 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.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 21 places
Functions with the same first-5-line body hash: slay_bench/potions.py:use, slay_bench/potions.py:use, slay_bench/potions.py:use, slay_bench/potions.py:use 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 …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 23 places
Functions with the same first-5-line body hash: slay_bench/relics.py:register, slay_bench/relics.py:register, slay_bench/relics.py:register, slay_bench/relics.py:register This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate …
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 26 places
Functions with the same first-5-line body hash: slay_bench/enemies_act2.py:select_move, slay_bench/enemies_act2.py:select_move, slay_bench/enemies_act2.py:select_move, slay_bench/enemies_act2.py:select_move This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: slay_bench/relics.py:on_pickup, slay_bench/relics.py:on_pickup, slay_bench/relics.py:on_pickup 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 sepa…
2 occurrences
repo-level (2 hits)
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: slay_bench/relics.py:on_attack_play, slay_bench/relics.py:on_attack, slay_bench/relics.py:on_attack, slay_bench/relics.py:on_attack This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Con…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: slay_bench/cards.py:end_of_turn_effect, slay_bench/cards.py:end_of_turn_effect, slay_bench/cards.py:end_of_turn_effect, slay_bench/cards.py:end_of_turn_effect This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 73 places
Functions with the same first-5-line body hash: slay_bench/relics_full.py:register, slay_bench/relics_full.py:register, slay_bench/relics_full.py:register, slay_bench/relics_full.py:register This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hy…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 76 places
Functions with the same first-5-line body hash: slay_bench/cards_silent.py:play, slay_bench/cards_silent.py:play, slay_bench/cards_silent.py:play, slay_bench/cards_silent.py:play This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Cons…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 83 places
Functions with the same first-5-line body hash: slay_bench/cards.py:upgrade, slay_bench/cards.py:upgrade, slay_bench/cards.py:upgrade, slay_bench/cards.py:upgrade This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 84 places
Functions with the same first-5-line body hash: slay_bench/cards.py:play, slay_bench/cards.py:play, slay_bench/cards.py:play, slay_bench/cards.py:play 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…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_pain_per_copy` in tests/test_combat.py:379
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: buy_potion
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
slay_bench/nodes.py:184
low System graph software Dead code conf 1.00 Possibly dead Python function: buy_relic
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
slay_bench/nodes.py:173
low System graph software Dead code conf 1.00 Possibly dead Python function: next_bool
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
slay_bench/rng.py:35
low System graph software Dead code conf 1.00 Possibly dead Python function: next_float
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
slay_bench/rng.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: unsubscribe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
slay_bench/events.py:55
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 Integrity conf 1.00 Stub function `on_death` (body is just `pass`/`return`) — slay_bench/enemies.py:43
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `play` (body is just `pass`/`return`) — slay_bench/cards_silent.py:743
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `register` (body is just `pass`/`return`) — slay_bench/relics_full.py:92
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: slay_bench/benchmark.py (1747 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: slay_bench/cards.py (1738 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/30503d7d-1b7c-499a-a328-4426c38bb918/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/30503d7d-1b7c-499a-a328-4426c38bb918/

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.