woodser/monero-ts

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.

17 of your 121 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.94s · analysis 23.44s · 9.6 MB · GitHub API rate-limit (preflight)

https://github.com/woodser/monero-ts · scanned 2026-06-05 12:48 UTC (5 days, 10 hours ago) · 10 languages

290 raw signals (116 security + 174 graph) 55th percentile · Typescript · medium (20-100K LoC) System graph score 76 (lower by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 79 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	55.0	0.25	13.75
`testing_score`	69.0	0.20	13.80
`documentation_score`	73.0	0.15	10.95
`practices_score`	67.0	0.15	10.05
`code_quality`	69.5	0.10	6.95
Overall		1.00	70.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 16 High 24 Medium 41 Low 60 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 106 System graph 79 Crowd 0 Layer: Software 101 Quality 33 Cicd 1 Security 12 Api 1 Frontend 37

Exclude dismissed / FP Exclude test files

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.

Commented-out code 5 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/`.

5 matching findings on this repo

info Commented-code block (8 lines) in src/test/TestMoneroWalletCommon.ts:1829
info Commented-code block (14 lines) in src/test/TestMoneroDaemonRpc.ts:744
info Commented-code block (7 lines) in src/main/ts/common/GenUtils.ts:695
info Commented-code block (7 lines) in src/main/ts/daemon/MoneroDaemon.ts:379
info Commented-code block (6 lines) in src/main/ts/daemon/MoneroDaemonRpc.ts:482

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

medium npm package `eslint-config-prettier` is 2 major version(s) behind (8.10.0 -> 10… package.json

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/03277d30-d4ef-430f-a159-b4d663028e02/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/03277d30-d4ef-430f-a159-b4d663028e02/

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.