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.

xuzhougeng/wispterm

https://github.com/xuzhougeng/wispterm · scanned 2026-06-16 01:03 UTC (2 months, 1 week ago)

65 raw signals (0 security + 65 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 26 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 0 Medium 11 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 26 Crowd 0 Layer: Software 3 Frontend 2 Hardware 2 Security 7 Cicd 3 Quality 9

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 51.8/100 with 77.8% coverage. It contains 1066 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 65 findings — concentrated in cicd (39), security (9), quality (9). Risk profile is high: 4 critical, 0 high, 22 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 21 of 26 actionable findings. 65 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in docs/ai.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

lines 136, 141

docs/ai.html:136, 141 (2 hits)

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in docs/ai.zh.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

lines 136, 141

docs/ai.zh.html:136, 141 (2 hits)

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — remote/src/worker.ts:34

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned

mlugg/setup-zig@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

7 files, 7 locations

.github/workflows/linux-release.yml:55

.github/workflows/macos-debug.yml:43

.github/workflows/macos-release-x86_64.yml:49

.github/workflows/macos-release.yml:42

.github/workflows/windows-debug.yml:39

.github/workflows/windows-release.yml:32

.github/workflows/wisptermctl-release.yml:42

CI/CD securitySupply chainGithub actions

medium System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

6 files, 6 locations

.github/workflows/linux-release.yml

.github/workflows/macos-release-x86_64.yml

.github/workflows/macos-release.yml

.github/workflows/pages.yml

.github/workflows/windows-release.yml

.github/workflows/wisptermctl-release.yml

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/themes.html:163

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

docs/themes.html:163 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in remote/src/client/theme.ts:74

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

remote/src/client/theme.ts:74 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in remote/src/client/views/console.ts:71

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

remote/src/client/views/console.ts:71 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in remote/src/client/views/login.ts:8

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

remote/src/client/views/login.ts:8 Direct innerhtml assignment

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — tools/kitty_graphics.py:87

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `DIST_DIR`, `HOST`, `PORT`, `REMOTE_COOKIE_SECURE`, `REMOTE_DATA_DIR`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 11 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 3, 14

remote/Dockerfile:3, 14 (2 hits)

containersPinned dependencies

low System graph cicd CI/CD security conf 1.00 26 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

8 files, 26 locations

.github/workflows/windows-release.yml:21, 36, 192, 199, 206, 213 (6 hits)

.github/workflows/macos-release.yml:30, 47, 167, 188, 191 (5 hits)

.github/workflows/pages.yml:28, 31, 34, 40 (4 hits)

.github/workflows/macos-debug.yml:40, 48, 117 (3 hits)

.github/workflows/macos-release-x86_64.yml:44, 54, 188 (3 hits)

.github/workflows/windows-debug.yml:34, 44, 72 (3 hits)

.github/workflows/linux-release.yml:74

.github/workflows/wisptermctl-release.yml:102

CI/CD securitySupply chainGithub actions

low System graph software Dead code conf 1.00 Possibly dead Python function: positive_int

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

tools/kitty_graphics.py:162

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — remote/src/server/index.ts:73

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph quality Complexity conf 1.00 Very large file: docs/themes-data.js (11781 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

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/02ea1ddc-bf2e-4670-b9c5-425d4e9e901f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/02ea1ddc-bf2e-4670-b9c5-425d4e9e901f/

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.