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.

pi-apps/pi-explorer

https://github.com/pi-apps/pi-explorer · scanned 2026-08-17 03:34 UTC (3 weeks, 5 days ago)

127 raw signals (0 security + 127 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks, 5 days ago · v1 · 118 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

80.0% cov · 118 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 29 Medium 62 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 118 Crowd 0 Layer: Frontend 5 Security 81 Hardware 3 Cicd 1 Quality 4 Dependencies 24

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 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (10 lines) in src/components/shared/InfoBanner.js:32 src/components/shared/InfoBanner.js:32

View all commented-out code findings →

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

12 matching findings on this repo

info TODO/FIXME marker in shipping code — config/webpack.config.prod.js:110 config/webpack.config.prod.js:110
info TODO/FIXME marker in shipping code — config/webpack.config.dev.js:106 config/webpack.config.dev.js:106
medium KSV-0001: Can elevate its own privileges — kubernetes/config/app.yaml
low KSV-0003: Default capabilities: some containers do not drop all — kubernetes/co…
low KSV-0004: Default capabilities: some containers do not drop any — kubernetes/co…
low KSV-0011: CPU not limited — kubernetes/config/app.yaml
medium KSV-0012: Runs as root user — kubernetes/config/app.yaml
medium KSV-0013: Image tag ":latest" used — kubernetes/config/app.yaml
high KSV-0014: Root file system is not read-only — kubernetes/config/app.yaml
low KSV-0018: Memory not limited — kubernetes/config/app.yaml
low KSV-0020: Runs with UID <= 10000 — kubernetes/config/app.yaml
low KSV-0021: Runs with GID <= 10000 — kubernetes/config/app.yaml

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/7761f1b5-e2c9-429e-ab22-8dea5f52ef43/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7761f1b5-e2c9-429e-ab22-8dea5f52ef43/

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.