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
86 of your 154 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 163.51s for a 325.9 MB repo slow.
  • Repobility's analysis ran in 44.16s after the clone landed.

OrcaSlicer/OrcaSlicer

https://github.com/OrcaSlicer/OrcaSlicer · scanned 2026-06-05 12:56 UTC (5 days, 10 hours ago) · 10 languages

472 raw signals (140 security + 332 graph) 11/13 scanners ran System graph score 84 (lower by 14)

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

Complete repo analysis

Last scanned 5 days, 10 hours ago · v2 · 161 actionable findings from 2 signal sources. 145 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
81.1
/100
Security checks
78
46 findings
System graph
84
88.9% cov · 115 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 46.0 0.20 9.20
documentation_score 66.0 0.15 9.90
practices_score 67.0 0.15 10.05
code_quality 62.0 0.10 6.20
Overall 1.00 70.1
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 16 Medium 13 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 46 System graph 115 Crowd 0 Layer: Quality 51 Cicd 12 Security 8 Software 61 Api 1 Frontend 25 Hardware 3

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.

Duplicates & near-duplicates 1 finding
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
1 matching finding on this repo
  • low Near-duplicate function bodies in 2 places
View all duplicates & near-duplicates findings →
Legacy markers 2 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
2 matching findings on this repo
  • low Old/deprecated-named symbol `_interopDefaultLegacy` in resources/web/include/sw…
  • low Old/deprecated-named symbol `_interopDefaultLegacy` in resources/web/guide/swip…
View all legacy markers findings →
Commented-out code 9 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
9 matching findings on this repo
  • info Commented-code block (11 lines) in resources/web/include/swiper/swiper-bundle.j…
  • info Commented-code block (11 lines) in resources/web/include/swiper/swiper-bundle.e…
  • info Commented-code block (7 lines) in resources/web/include/swiper/modules/free-mod…
  • info Commented-code block (11 lines) in resources/web/include/swiper/modules/mousewh…
  • info Commented-code block (17 lines) in resources/web/model/model.js:14
  • info Commented-code block (11 lines) in resources/web/guide/swiper/swiper-bundle.js:…
  • info Commented-code block (11 lines) in resources/web/guide/swiper/swiper-bundle.esm…
  • info Commented-code block (7 lines) in resources/web/guide/swiper/modules/free-mode/…
  • info Commented-code block (11 lines) in resources/web/guide/swiper/modules/mousewhee…
View all commented-out code 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/417496a0-0b0f-4e54-956c-c03b736e1da9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/417496a0-0b0f-4e54-956c-c03b736e1da9/

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.