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.

rexlunae/RustyClaw

https://github.com/rexlunae/RustyClaw · scanned 2026-06-15 23:50 UTC (2 months, 3 weeks ago)

30 raw signals (0 security + 30 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 70.3/100 with 88.9% coverage. It contains 533 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 30 findings — concentrated in security (14), quality (6), cicd (5). Risk profile is high: 6 critical, 7 high, 6 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 22 of 24 actionable findings. 30 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 Possible secret in Cargo.toml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
Cargo.toml:147
critical System graph security Secrets conf 1.00 4 occurrences Possible secret in crates/rustyclaw-core/src/security/leak_detector.rs
Detected pattern matching github_token. Rotate the credential and move to a secret manager.
lines 547, 636, 643, 688
crates/rustyclaw-core/src/security/leak_detector.rs:547, 636, 643, 688 (4 hits)
critical System graph security Secrets conf 1.00 Possible secret in crates/rustyclaw-gateway/src/main.rs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
crates/rustyclaw-gateway/src/main.rs:197
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/rustyclaw-core/src/tools/definitions.rs:337
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/rustyclaw-core/src/tools/definitions.rs:337 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/rustyclaw-desktop/src/app_support.rs:478
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/rustyclaw-desktop/src/app_support.rs:478 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/rustyclaw-desktop/src/components/chat.rs:55
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/rustyclaw-desktop/src/components/chat.rs:55 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in crates/rustyclaw-desktop/src/components/mod.rs:63
Found a known-risky pattern (eval_used). Review and replace if possible.
crates/rustyclaw-desktop/src/components/mod.rs:63 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in crates/rustyclaw-core/src/sandbox/platform.rs:153
Found a known-risky pattern (exec_used). Review and replace if possible.
crates/rustyclaw-core/src/sandbox/platform.rs:153 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in crates/rustyclaw-core/src/tools/definitions.rs:812
Found a known-risky pattern (exec_used). Review and replace if possible.
crates/rustyclaw-core/src/tools/definitions.rs:812 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in README.md:60
Found a known-risky pattern (exec_used). Review and replace if possible.
README.md:60 Exec used
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 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/website.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in crates/rustyclaw-core/src/secrets/vault_ext.rs:184
Found a known-risky pattern (weak_hash). Review and replace if possible.
crates/rustyclaw-core/src/secrets/vault_ext.rs:184 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 59 placeholder/mock markers across 33 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
19 test file(s) for 306 source file(s) (ratio 0.06). Consider adding integration or unit tests for critical paths.
Coverage
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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:35 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1.85-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 27, 30, 33, 39
.github/workflows/website.yml:27, 30, 33, 39 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph software Dead code conf 1.00 Possibly dead Python function: sanitize
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
contrib/nanobot-prompt-guard/prompt_guard.py:215
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
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/5e23ab4f-4b6b-479f-ad7a-d25da6631ac5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5e23ab4f-4b6b-479f-ad7a-d25da6631ac5/

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.