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

Soypete/DragonSlayer

https://github.com/Soypete/DragonSlayer · scanned 2026-06-16 00:18 UTC (2 months, 2 weeks ago)

16 raw signals (0 security + 16 graph)

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

Complete repo analysis

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

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

Showing 11 of 16 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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.local.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/settings.local.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 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 security conf 1.00 Insecure pattern 'node_child_process' in src/ai/augury.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/ai/augury.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/ai/oracle.ts:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/ai/oracle.ts:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/ai/squire.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/ai/squire.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/repo/runner.ts:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/repo/runner.ts:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/repo/toolchain.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/repo/toolchain.ts:11 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
low System graph software Dead code conf 1.00 Possibly dead Python function: shed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/repo/__fixtures__/serpents-spire/spire/scales.py:4
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/a56bc781-c34b-4c4c-9c4f-794d433e808f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a56bc781-c34b-4c4c-9c4f-794d433e808f/

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.