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

vitorbaptista/shellshare

https://github.com/vitorbaptista/shellshare · scanned 2026-06-16 00:51 UTC (2 months, 1 week ago)

55 raw signals (0 security + 55 graph)

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

Complete repo analysis

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

JSON
Combined
64.9
/100
Security checks
65
0 findings
System graph
65
88.9% cov · 27 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 0 Medium 4 Low 16 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 27 Crowd 0 Layer: Software 7 Frontend 2 Hardware 4 Cicd 3 Quality 10 Security 1
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 64.9/100 with 88.9% coverage. It contains 574 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 55 findings — concentrated in cicd (29), quality (12), software (7). Risk profile is low: 0 critical, 0 high, 15 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 20 of 27 actionable findings. 55 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.

medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: AGENTS.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
AGENTS.md:14 Supply chainAgents md
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 12 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 12 locations
.github/workflows/release.yml:51, 56, 103, 108, 192, 199 (6 hits)
.github/workflows/e2e-windows.yml:22, 25, 31 (3 hits)
.github/workflows/e2e.yml:31, 34, 40 (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
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 22 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: 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:13 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1-slim-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 16 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.
3 files, 16 locations
.github/workflows/release.yml:48, 66, 100, 116, 122, 128, 134, 164, +6 more (14 hits)
.github/workflows/e2e-windows.yml:19
.github/workflows/e2e.yml:28
CI/CD securitySupply chainGithub actions
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: e2e/benchmark_fanout.py:close, e2e/benchmark_fanout.py:close 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.
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: bench_broadcast_latency
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: bench_cli_latency
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark.py:139
low System graph software Dead code conf 1.00 Possibly dead Python function: bench_cli_throughput
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark.py:194
low System graph software Dead code conf 1.00 Possibly dead Python function: bench_ingest_ack_rtt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: bench_ingest_throughput
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark.py:168
low System graph software Dead code conf 1.00 Possibly dead Python function: bench_join_catchup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark.py:245
low System graph software Dead code conf 1.00 Possibly dead Python function: blast
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
e2e/benchmark_fanout.py:478
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 — npm/scripts/prepare-packages.js:59
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
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/bb0b3df3-a2df-45d3-a8e5-27c1aafd9d8f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/bb0b3df3-a2df-45d3-a8e5-27c1aafd9d8f/

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.