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

SovereignSignal/clawbytes

https://github.com/SovereignSignal/clawbytes · scanned 2026-06-16 00:18 UTC (2 months, 2 weeks ago)

45 raw signals (0 security + 45 graph)

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

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 36 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
Combined
77.4
/100
Security checks
77
0 findings
System graph
77
88.9% cov · 36 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 1 Medium 8 Low 24 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 36 Crowd 0 Layer: Software 12 Api 1 Hardware 4 Frontend 1 Security 3 Cicd 1 Quality 14
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 77.4/100 with 88.9% coverage. It contains 645 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 45 findings — concentrated in quality (21), software (14), hardware (4). Risk profile is high: 0 critical, 1 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 33 of 36 actionable findings. 45 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 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:23 containersRemote installer
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 security security conf 1.00 Insecure pattern 'subprocess_shell_true' in clawbytes_daily.py:119
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
clawbytes_daily.py:119 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in clawbytes_threads.py:995
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
clawbytes_threads.py:995 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/supervisor.py:304
`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
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Integrity conf 1.00 23 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CLAUDE_CREDENTIALS`, `CLAUDE_MODEL`, `CLAWBYTES_CURATOR_API_KEY`, `CLAWBYTES_CURATOR_LANES`, `CLAWBYTES_CURATOR_MAX_TOKENS`, `CLAWBYTES_CURATOR_MODEL`, `CLAWBYTES_CURATOR_TIMEOUT`, `CLAWBYTES_CURATOR_URL` + 15 more. Add them (with a placeholder/co…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
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 350 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: python:3.11-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:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: clawbytes_threads.py:cred, clawbytes_daily.py:cred This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: scripts/claw-leaderboard-monitor.py:save_state, scripts/claw-bsky-monitor.py:save_state, scripts/claw-pagewatch-monitor.py:save_state, scripts/claw-registry-monitor.py:save_state This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: scripts/claw-leaderboard-monitor.py:load_state, scripts/claw-bsky-monitor.py:load_state, scripts/claw-pagewatch-monitor.py:load_state, scripts/claw-registry-monitor.py:load_state This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `hours_old` in scripts/claw_notion_signals.py:222
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 software Dead code conf 1.00 Possibly dead Python function: category_take
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
clawbytes_threads.py:1787
low System graph software Dead code conf 1.00 Possibly dead Python function: enrich_ship_with_notion
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/claw_notion_signals.py:383
low System graph software Dead code conf 1.00 Possibly dead Python function: extract_any_url
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/claw-notion-sync.py:144
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: handle_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
content-engine/src/claw_content_engine/feed_reports.py:66
content-engine/src/claw_content_engine/loaders.py:101
scripts/claws_digest.py:1052
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_endtag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
content-engine/src/claw_content_engine/feed_reports.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_starttag
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
content-engine/src/claw_content_engine/feed_reports.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: load_cached_signals
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/claw_notion_signals.py:174
low System graph software Dead code conf 1.00 Possibly dead Python function: reddit_counts
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
clawbytes_threads.py:957
low System graph software Dead code conf 1.00 Possibly dead Python function: render_signal_item
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/claws_digest.py:404
low System graph software Dead code conf 1.00 Possibly dead Python function: richer_community_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
clawbytes_threads.py:628
low System graph software Dead code conf 1.00 Possibly dead Python function: save_cached_signals
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/claw_notion_signals.py:183
low System graph software Dead code conf 1.00 Possibly dead Python function: source_badge
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
clawbytes_threads.py:1799
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 quality Complexity conf 1.00 Very large file: clawbytes_threads.py (2475 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/a5c6ee4a-8672-4bc3-a706-143fbc394881/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a5c6ee4a-8672-4bc3-a706-143fbc394881/

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.