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.

satemafac/njangi-on-chain

https://github.com/satemafac/njangi-on-chain · scanned 2026-06-16 00:03 UTC (2 months, 3 weeks ago)

315 raw signals (0 security + 315 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 311 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 311 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 90 Medium 34 Low 94 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 311 Crowd 0 Layer: Frontend 75 Hardware 2 Security 11 Cicd 1 Quality 123 Api 99

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.

Legacy markers 3 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.

3 matching findings on this repo

low Old/deprecated-named symbol `canonicalOrLegacy` in whatsapp-bot-backend/src/con…
low Old/deprecated-named symbol `canonicalOrLegacy` in scripts/validate-env.mjs:37
low Old/deprecated-named symbol `canonicalOrLegacy` in src/config/public-env.ts:113

View all legacy markers findings →

Commented-out code 77 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 (11 lines) in next.config.js:7
info Commented-code block (7 lines) in whatsapp-bot-backend/src/pages/api/whatsapp/w…
info Commented-code block (6 lines) in whatsapp-bot-backend/src/services/cycle-remin…
info Commented-code block (5 lines) in scripts/smoke-testnet.mjs:2
info Commented-code block (7 lines) in scripts/cycle-finalized-notifier.mjs:4
info Commented-code block (14 lines) in scripts/migrate-postgres.mjs:6
info Commented-code block (10 lines) in scripts/bootstrap-package.mjs:7
info Commented-code block (21 lines) in scripts/generate-secrets.mjs:6
info Commented-code block (6 lines) in scripts/stripe-bootstrap.mjs:6
info Commented-code block (5 lines) in scripts/validate-env.mjs:102
info Commented-code block (5 lines) in src/config/public-env.ts:21
info Commented-code block (6 lines) in src/middleware/admin-auth.middleware.ts:100

View all commented-out code findings →

Config drift 9 findings

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.

9 matching findings on this repo

low Stray `console.log` in TS/JS — whatsapp-bot-backend/src/config/config.ts:6
low Stray `console.log` in TS/JS — src/services/network-config.ts:176
medium Insecure pattern 'weak_hash' in next.config.js:115 next.config.js:115
info Commented-code block (11 lines) in next.config.js:7
low Old/deprecated-named symbol `canonicalOrLegacy` in whatsapp-bot-backend/src/con…
low Old/deprecated-named symbol `canonicalOrLegacy` in src/config/public-env.ts:113
info Commented-code block (5 lines) in src/config/public-env.ts:21
high Dangling fetch: POST /api/circles/swap-config (src/components/StablecoinSwapFor…
high Dangling fetch: GET /api/circles/swap-config?${queryParams} (src/services/swap-…

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/4dd67504-76cc-454d-a10f-a3a5dce2913b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4dd67504-76cc-454d-a10f-a3a5dce2913b/

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.