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.

swompythesecond/BrowserCoin

https://github.com/swompythesecond/BrowserCoin · scanned 2026-06-16 00:26 UTC (2 months, 2 weeks ago)

64 raw signals (0 security + 64 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 64 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 24 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 64 Crowd 0 Layer: Frontend 7 Security 22 Cicd 1 Quality 23 Api 11

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 16 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 vitest.config.ts:12
info Commented-code block (5 lines) in examples/send-tx.mjs:6
info Commented-code block (6 lines) in src/node.ts:439
info Commented-code block (5 lines) in src/main.ts:71
info Commented-code block (13 lines) in src/crypto/pow.ts:37
info Commented-code block (9 lines) in src/miner/miner.worker.ts:43
info Commented-code block (6 lines) in src/miner/controller.ts:232
info Commented-code block (7 lines) in src/ui/miner.ts:397
info Commented-code block (6 lines) in src/ui/home.ts:459
info Commented-code block (5 lines) in src/chain/mempool.ts:79
info Commented-code block (7 lines) in src/chain/testutil.ts:60
info Commented-code block (7 lines) in src/chain/consensus.test.ts:73

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

info Commented-code block (6 lines) in vitest.config.ts:12

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/576e7be4-f536-4f74-aefa-f399e6af4686/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/576e7be4-f536-4f74-aefa-f399e6af4686/

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.