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.

samsmithyeah/tapsmith

https://github.com/samsmithyeah/tapsmith · scanned 2026-06-16 00:01 UTC (2 months, 3 weeks ago)

165 raw signals (0 security + 165 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 123 actionable findings from 1 signal source. 42 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 · 123 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 49 Low 31 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 123 Crowd 0 Layer: Frontend 13 Security 37 Cicd 3 Quality 70

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 40 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 (8 lines) in website/scripts/sync-docs.mjs:6
info Commented-code block (5 lines) in test-app/plugins/with-webview-debugging.js:1
info Commented-code block (5 lines) in packages/tapsmith/vite.config.ui-mode.ts:18
info Commented-code block (6 lines) in packages/tapsmith/scripts/fetch-bezels.mjs:151
info Commented-code block (5 lines) in packages/tapsmith/src/verify-ios-network.ts:1…
info Commented-code block (5 lines) in packages/tapsmith/src/watch.ts:187
info Commented-code block (5 lines) in packages/tapsmith/src/ios-trust-probe.ts:53
info Commented-code block (5 lines) in packages/tapsmith/src/worker-runner.ts:126
info Commented-code block (5 lines) in packages/tapsmith/src/element-handle.ts:882
info Commented-code block (7 lines) in packages/tapsmith/src/setup-ios-device.ts:401
info Commented-code block (5 lines) in packages/tapsmith/src/session-preflight.ts:110
info Commented-code block (9 lines) in packages/tapsmith/src/grpc-client.ts:299

View all commented-out code findings →

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

5 matching findings on this repo

low Stray `console.log` in TS/JS — packages/tapsmith/src/configure-ios-network.ts:1…
medium Insecure pattern 'node_child_process' in packages/tapsmith/src/configure-ios-ne… packages/tapsmith/src/configure-ios-network.ts:19
info Commented-code block (5 lines) in packages/tapsmith/vite.config.ui-mode.ts:18
info Commented-code block (6 lines) in packages/tapsmith/src/configure-ios-network.t…
info Commented-code block (7 lines) in packages/tapsmith/src/__tests__/config.test.t…

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/f44a26d1-87e8-425b-b391-04bf2d56e575/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f44a26d1-87e8-425b-b391-04bf2d56e575/

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.