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
159 of your 218 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 34.78s for a 74.8 MB repo slow.
  • Repobility's analysis ran in 18.5s after the clone landed.

Vector35/binaryninja-api

https://github.com/Vector35/binaryninja-api · scanned 2026-06-05 23:53 UTC (4 days, 5 hours ago) · 10 languages

631 raw signals (205 security + 426 graph) 11/13 scanners ran 46th percentile · C · huge (>500K LoC) System graph score 90 (lower by 25)

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

Complete repo analysis

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

JSON
Combined
82.3
/100
Security checks
75
60 findings
System graph
90
77.8% cov · 191 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 26.0 0.20 5.20
documentation_score 67.0 0.15 10.05
practices_score 85.0 0.15 12.75
code_quality 27.0 0.10 2.70
Overall 1.00 64.7
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 0 High 10 Medium 11 Low 92 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 60 System graph 191 Crowd 0 Layer: Quality 210 Security 7 Cicd 2 Software 29 Api 1 Frontend 2

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 4 findings
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.
4 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 5 places
  • low Near-duplicate function bodies in 4 places
  • low Near-duplicate function bodies in 3 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 94 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/`.
12 matching findings on this repo
  • info Commented-code block (6 lines) in stubs/generate_stubs.py:3
  • info Commented-code block (6 lines) in arch/mips/mips/unittest/unitTest.py:193
  • info Commented-code block (5 lines) in arch/arm64/test_gen.py:212
  • info Commented-code block (13 lines) in arch/arm64/misc/neon_intrins.py:239
  • info Commented-code block (12 lines) in arch/armv7/thumb2_disasm/generator.py:502
  • info Commented-code block (6 lines) in arch/x86/code_generator/parse-iform-types.py:…
  • info Commented-code block (6 lines) in python/associateddatastore.py:3
  • info Commented-code block (6 lines) in python/filemetadata.py:3
  • info Commented-code block (6 lines) in python/typecontainer.py:3
  • info Commented-code block (6 lines) in python/metadata.py:3
  • info Commented-code block (6 lines) in python/database.py:4
  • info Commented-code block (6 lines) in python/__init__.py:3
View all commented-out code findings →
Config drift 1 finding
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
1 matching finding on this repo
  • low Possibly dead Python function: config_initiated sphinx_rtd/__init__.py:27
View all config drift 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/ba8c1155-b910-4ac6-8158-d21018b737ac/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ba8c1155-b910-4ac6-8158-d21018b737ac/

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.