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

slayerlabs/slayer

https://github.com/slayerlabs/slayer · scanned 2026-06-16 00:15 UTC (2 months, 2 weeks ago)

64 raw signals (23 security + 41 graph)

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

Complete repo analysis

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

JSON
Combined
96.0
/100
Security checks
96
7 findings
System graph
96
77.8% cov · 38 findings
Critical
2
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 2 High 3 Medium 11 Low 28 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 38 Crowd 0 Layer: Quality 26 Security 3 Software 14 Frontend 1 Cicd 1
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 96.0/100 with 77.8% coverage. It contains 454 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 41 findings — concentrated in quality (20), software (17), security (2). Risk profile is high: 0 critical, 1 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 44 of 45 actionable findings. 115 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 Security checks quality Practices conf 0.82 Foundry mined mock as real or placeholder: slayerlabs/slayer
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
critical Security checks security auth conf 0.78 4 occurrences Foundry mined security auth guardrail gaps: slayerlabs/slayer
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
4 occurrences
repo-level (4 hits)
high Security checks quality Practices conf 0.84 8 occurrences Foundry mined bad chains: slayerlabs/slayer
Comment chain pattern product: bad_chains Repo: slayerlabs/slayer Thread: slayerlabs/slayer#34 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts, link…
8 occurrences
repo-level (8 hits)
high Security checks quality Testing conf 0.78 Foundry mined test ci gap after feedback: slayerlabs/slayer
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: assumption_check Repo: …
high System graph security security conf 1.00 Insecure pattern 'eval_used' in app/eksperymenty/log.jsx:77
Found a known-risky pattern (eval_used). Review and replace if possible.
app/eksperymenty/log.jsx:77 Eval used
medium Security checks quality Practices conf 0.62 26 occurrences Foundry mined assumption checks: slayerlabs/slayer
Comment chain pattern product: assumption_checks Repo: slayerlabs/slayer Thread: slayerlabs/slayer#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts, link_quality…
26 occurrences
repo-level (26 hits)
medium Security checks quality maintenance conf 0.70 14 occurrences Foundry mined blueprint gap alignment: slayerlabs/slayer
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
14 occurrences
repo-level (14 hits)
medium Security checks quality Practices conf 0.70 20 occurrences Foundry mined unresolved feedback: slayerlabs/slayer
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
20 occurrences
repo-level (20 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — app/styl/examples.jsx:24
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app/zespol/join.jsx:61
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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bench/build_v3_mix.py:183
`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 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 17 placeholder/mock markers across 4 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 78 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 174 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 Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: bench/heldout_check.py:audit_heldout, bench/decon_audit.py:audit_file 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.
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `holdout_v1` in bench/make_style_disjoint.py:5
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 `knowledge_probe_v1` in app/wiedza/page.jsx:64
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 `polnative_v1` in app/leaderboard/polnative.jsx:17
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 `polnative_v1` in bench/polnative_eval.py:4
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 `polnative_v1` in bench/polnative_leaderboard.py:4
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 `polnative_v1` in bench/polnative_report.py:4
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 `polnative_v1` in bench/polnative_strategy.py:4
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 `probe_v1` in bench/decon_audit.py:9
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 `probe_v1` in bench/knowledge_probe.py:9
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 `probe_v1` in bench/verify_probe_golds.py:2
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: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/signup_server.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: do_OPTIONS
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/signup_server.py:36
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/signup_server.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: explode
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/entigraph_augment.py:160
low System graph software Dead code conf 1.00 Possibly dead Python function: explode
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/entigraph_hops.py:149
low System graph software Dead code conf 1.00 Possibly dead Python function: load_arc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: load_belebele
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: load_belebele_en
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: load_include
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:68
low System graph software Dead code conf 1.00 Possibly dead Python function: load_llmzszl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:33
low System graph software Dead code conf 1.00 Possibly dead Python function: load_mmlu
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: load_pes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bench/bench_mcq.py:53
low System graph software Dead code conf 1.00 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.
bench/signup_server.py:35
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: work
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
bench/mtbench_pl.py:97
bench/spotcheck_entigraph.py:116
bench/verify_external_sft.py:91
bench/verify_probe_golds.py:85
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
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/497da7f2-e3b2-4892-a4e7-702e37d9bb98/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/497da7f2-e3b2-4892-a4e7-702e37d9bb98/

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.