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.
Sign up free Scan another repo

UstaLabs/supermux

https://github.com/UstaLabs/supermux · scanned 2026-06-16 00:46 UTC (2 months, 1 week ago)

158 raw signals (3 security + 155 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
60.4
/100
Security checks
60
3 findings
System graph
60
100.0% cov · 153 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 2 Medium 52 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 153 Crowd 0 Layer: Quality 92 Api 1 Frontend 18 Hardware 4 Security 39 Cicd 2
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 60.4/100 with 100.0% coverage. It contains 2764 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 155 findings — concentrated in quality (89), security (39), frontend (18). Risk profile is high: 0 critical, 1 high, 52 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 79 of 156 actionable findings. 158 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.

high Security checks quality Practices conf 0.84 Foundry mined bad chains: UstaLabs/supermux
Comment chain pattern product: bad_chains Repo: UstaLabs/supermux Thread: UstaLabs/supermux#1 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_ha…
high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
Dockerfile:46 containersRemote installer
medium Security checks quality maintenance conf 0.70 Foundry mined blueprint gap alignment: UstaLabs/supermux
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
medium Security checks quality Practices conf 0.70 Foundry mined unresolved feedback: UstaLabs/supermux
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: assu…
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/migrate-from-running-broker.ts:73
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/channels/web/update-routes.test.ts:69
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/cli-update.test.ts:53
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/lsp/install-dart-sdk.ts:31
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/core/session-manager/download.ts:57
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/web-app/src/api/client.ts:180
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/web-app/src/composables/useNotifications.ts:86
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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/login-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 83, 90, 97
.github/workflows/release.yml:83, 90, 97 (3 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 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.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/migrate-from-running-broker.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/migrate-from-running-broker.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/reclaim-agent-homes.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/reclaim-agent-homes.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/agents/codex/spawn.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/agents/codex/spawn.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/agents/cursor/runner.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/agents/cursor/runner.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/agents/opencode/spawn.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/agents/opencode/spawn.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/editor/fs-service.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/editor/fs-service.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/editor/repo-scanner.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/editor/repo-scanner.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/editor/workdir-diff.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/editor/workdir-diff.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/git/branches.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/git/branches.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/git/integrate.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/git/integrate.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/git/remote.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/git/remote.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/git/repo-info.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/git/repo-info.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/lsp/install.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/lsp/install.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/lsp/server.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/lsp/server.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/models/discovery.ts:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/models/discovery.ts:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/plugins/adapters/codex.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/plugins/adapters/codex.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/plugins/lifecycle.ts:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/plugins/lifecycle.ts:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/review/anchor.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/review/anchor.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/session-manager/post-spawn-keys.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/session-manager/post-spawn-keys.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/session-manager/spawn-helper.ts:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/session-manager/spawn-helper.ts:28 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/session-manager/tmux.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/session-manager/tmux.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/slash-commands/providers/claude.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/slash-commands/providers/claude.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/worktree/finish.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/worktree/finish.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/worktree/gc.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/worktree/gc.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/worktree/manager.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/worktree/manager.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/core/worktree/verify.ts:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/core/worktree/verify.ts:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main.ts:66
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/main.ts:66 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/shared/preflight.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/shared/preflight.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/web-app/vite.config.ts:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/web-app/vite.config.ts:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'vue_v_html' in src/web-app/src/components/MessageText.vue:24
Found a known-risky pattern (vue_v_html). Review and replace if possible.
src/web-app/src/components/MessageText.vue:24 Vue v html
low System graph quality Integrity conf 1.00 40 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BUN_INSTALL`, `CLAUDE_SESSION_ID`, `CURATOR_WINDOW_HOURS`, `CURSOR_API_KEY`, `FLUTTER_ROOT`, `HOME`, `INVOCATION_ID`, `MUX_AGENT_KIND` + 32 more. 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 62 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 Docker base image is tag-pinned but not digest-pinned: oven/bun:1
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:19 containersPinned dependencies
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `coreLegacy` in scripts/migrate-to-mux.ts:66
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in src/core/agents/codex/auth.ts:6
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in src/core/agents/cursor/auth.ts:8
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in tests/agents/codex-auth.test.ts:31
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in tests/agents/cursor-auth.test.ts:35
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in tests/spawn-codex-attachments.test.ts:28
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in tests/spawn-pa.test.ts:84
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `oauth_copy` in tests/supervisor.test.ts:75
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
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 — scripts/asset-probe.ts:56
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/dump-last-24h.ts:16
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/dump-ws-frames.ts:53
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-logo-assets.ts:72
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-static-manifest.ts:44
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-versions-json.ts:12
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/migrate-from-running-broker.ts:43
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/migrate-to-mux.ts:119
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/pair.ts:31
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/plugin.ts:44
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/reclaim-agent-homes.ts:30
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/revoke.ts:11
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli.ts:35
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/core/lsp/install-dart-sdk.ts:22
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/web-app/scripts/check-bundle-size.ts:13
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/ui/composer-attachment.spec.ts:47
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/ui/push-banner.spec.ts:33
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/ui/voice-recorder.spec.ts:28
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: src/channels/web/index.ts (1882 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/main.ts (2931 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/865d742e-ef47-4f32-b21e-002ce2927056/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/865d742e-ef47-4f32-b21e-002ce2927056/

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.