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.

samuelgradientai-sys/clawksis-agent

https://github.com/samuelgradientai-sys/clawksis-agent · scanned 2026-06-16 00:04 UTC (2 months, 3 weeks ago)

1213 raw signals (0 security + 1213 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 97 Medium 171 Low 424 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1186 Crowd 0 Layer: Software 23 Frontend 84 Network 2 Hardware 4 Security 161 Cicd 1 Quality 847 Api 64

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.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

Legacy markers 25 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

12 matching findings on this repo

low Old/deprecated-named symbol `get_legacy` in tests/test_tui_gateway_server.py:21…
low Old/deprecated-named symbol `test_extra_body_override_legacy` in tests/provider…
low Old/deprecated-named symbol `rs_legacy` in tests/run_agent/test_codex_xai_oauth…
low Old/deprecated-named symbol `user_legacy` in tests/clawk_cli/test_gateway_servi…
low Old/deprecated-named symbol `test_env_override_wins_over_legacy` in tests/clawk…
low Old/deprecated-named symbol `test_corrupt_owner_pid_falls_back_to_legacy` in te…
low Old/deprecated-named symbol `test_canonical_wins_over_legacy` in tests/tools/te…
low Old/deprecated-named symbol `clear_legacy` in tests/tools/test_checkpoint_manag…
low Old/deprecated-named symbol `expected_legacy` in tests/tools/test_delegate.py:2…
low Old/deprecated-named symbol `test_load_prefill_messages_prefers_top_level_over_…
low Old/deprecated-named symbol `MyLegacy` in tests/gateway/test_platform_registry.…
low Old/deprecated-named symbol `test_text_as_dict_legacy` in tests/gateway/test_di…

View all legacy markers findings →

Commented-out code 408 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 (6 lines) in run_agent.py:49
info Commented-code block (5 lines) in toolsets.py:581
info Commented-code block (5 lines) in clawk_constants.py:91
info Commented-code block (8 lines) in cli.py:23573
info Commented-code block (8 lines) in batch_runner.py:921
info Commented-code block (6 lines) in tests/conftest.py:266
info Commented-code block (5 lines) in tests/test_install_sh_setup_wizard_tty_probe.…
info Commented-code block (6 lines) in tests/test_tui_gateway_ws.py:12
info Commented-code block (5 lines) in tests/test_packaging_metadata.py:7
info Commented-code block (9 lines) in tests/test_yuanbao_pipeline.py:1001
info Commented-code block (6 lines) in tests/docker/test_dashboard.py:150
info Commented-code block (5 lines) in tests/docker/test_container_restart.py:115

View all commented-out code findings →

Config drift 61 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 `truncate` class without `title=` for hover reveal — apps/desktop/src/app/setti…
info `truncate` class without `title=` for hover reveal — web/src/pages/ConfigPage.t…
medium Insecure pattern 'subprocess_shell_true' in clawk_cli/tools_config.py:1175 clawk_cli/tools_config.py:1175
low Very large file: tests/clawk_cli/test_tools_config.py (1996 lines)
low Very large file: clawk_cli/tools_config.py (5978 lines)
low Very large file: clawk_cli/config.py (8337 lines)
low Very large file: gateway/config.py (2139 lines)
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: optional-skills/security/sherlock… optional-skills/security/sherlock/SKILL.md:203
high Agent instruction/config may expose a secret: optional-skills/email/agentmail/S… optional-skills/email/agentmail/SKILL.md:89
high Agent instruction/config may expose a secret: optional-skills/mlops/chroma/SKIL… optional-skills/mlops/chroma/SKILL.md:161
high Agent instruction/config may expose a secret: optional-skills/mlops/saelens/SKI… optional-skills/mlops/saelens/SKILL.md:166

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/39b4da4a-719c-43a8-8747-48e4f97a4753/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/39b4da4a-719c-43a8-8747-48e4f97a4753/

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.