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.

zubair-io/Maple

https://github.com/zubair-io/Maple · scanned 2026-06-16 01:14 UTC (2 months, 1 week ago)

441 raw signals (0 security + 441 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 432 actionable findings from 1 signal source. 9 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 · 432 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 19 Low 100 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 432 Crowd 0 Layer: Software 1 Frontend 75 Hardware 4 Security 3 Cicd 1 Quality 348

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.

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 repo-level

View all duplicates & near-duplicates findings →

Commented-out code 309 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 (5 lines) in test-fixtures/face-clustering/scripts/generat…
info Commented-code block (8 lines) in src/api/tests/backup-ingest-helpers.ts:108
info Commented-code block (12 lines) in src/api/tests/images-repo-meilisearch.test.t…
info Commented-code block (5 lines) in src/api/tests/people-route.test.ts:248
info Commented-code block (7 lines) in src/api/tests/assets-restore.test.ts:264
info Commented-code block (10 lines) in src/api/tests/assets-upload.test.ts:55
info Commented-code block (6 lines) in src/api/tests/backup-rendered.test.ts:68
info Commented-code block (5 lines) in src/api/tests/folders-trash-list.test.ts:65
info Commented-code block (5 lines) in src/api/tests/backup-ingest-cloud-dedup.test.…
info Commented-code block (6 lines) in src/api/tests/backup-ingest.test.ts:9
info Commented-code block (7 lines) in src/api/tests/workers-status-perf.test.ts:123
info Commented-code block (10 lines) in src/api/tests/indexer-id.test.ts:103

View all commented-out code findings →

Config drift 10 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.

10 matching findings on this repo

low Stray `console.log` in TS/JS — src/api/tests/observability-config.repo.test.ts:…
low Stray `console.log` in TS/JS — src/api/src/enrichment/enrichment-config.repo.te…
low Stray `console.log` in TS/JS — src/api/src/ffi/ffi-pool-config.repo.test.ts:113
low Stray `console.log` in TS/JS — src/api/src/workers/dedupe-config.repo.test.ts:42
low Stray `console.log` in TS/JS — src/api/src/fs/mirror-config.test.ts:49
info Commented-code block (5 lines) in src/api/src/workers/stage-config.ts:60
info Commented-code block (6 lines) in src/api/src/workers/discover/discover-config.…
info Commented-code block (5 lines) in src/web/projects/maple/src/app/app.config.ts:…
info Commented-code block (6 lines) in src/web/projects/maple-common/src/lib/observa…
info Commented-code block (5 lines) in src/web/projects/maple-common/src/lib/observa…

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/5a77b6ce-91c2-4003-b49f-689299ed86b2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5a77b6ce-91c2-4003-b49f-689299ed86b2/

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.