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

casdoor/casdoor

https://github.com/casdoor/casdoor · scanned 2026-05-15 13:43 UTC (2 weeks, 6 days ago) · 10 languages

274 findings (41 legacy + 233 scanner) 0th percentile · Go · large (100-500K LoC) Scanner says 61 (lower by 3)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 33 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
62.3
/100
Repobility
64
33 legacy
9-layer
61
100.0% cov · 0 gaps
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 72.2 0.25 18.05
testing_score 15.0 0.20 3.00
documentation_score 60.0 0.15 9.00
practices_score 90.0 0.15 13.50
code_quality 57.8 0.10 5.78
Overall 1.00 58.3
Calibrated penalty buckets (security_score): agent: 2.3 · docker: 19.9 · journey: 5.6
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 20 Medium 6 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 33 9-layer 0 Crowd 0 Layer: Security 3 Cicd 13 Quality 17

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 17 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium Agent control bridge may listen on a network interface without visible auth web/src/provider/ScanProviderFields.js:11
  • medium React interval is created without an explicit cleanup web/src/auth/LoginPage.js:414
  • medium Duplicated implementation block across source files idp/custom.go:76
  • medium Duplicated implementation block across source files idp/bilibili.go:149
  • medium Duplicated implementation block across source files controllers/user_upload.go:33
  • medium Duplicated implementation block across source files controllers/transaction.go:39
  • medium Duplicated implementation block across source files controllers/subscription.go:40
  • medium Duplicated implementation block across source files controllers/server_sync.go:16
  • medium Duplicated implementation block across source files controllers/role_upload.go:9
  • medium Duplicated implementation block across source files controllers/product.go:106
  • medium Duplicated implementation block across source files controllers/permission_upload.go:9
  • medium Duplicated implementation block across source files controllers/payment.go:39
View all fragile runtime findings →
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/0fd5592b-06d3-4fcb-8fbb-58888b2ad746/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0fd5592b-06d3-4fcb-8fbb-58888b2ad746/

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.