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.

schollz/croc

https://github.com/schollz/croc · scanned 2026-07-23 10:34 UTC (5 days, 6 hours ago)

26 raw signals (0 security + 26 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 6 hours ago · v5 · last Δ +6.9 (diff) · 23 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

60.0% cov · 23 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 18 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 23 Crowd 0 Layer: Security 12 Network 3 Hardware 2 Cicd 3 Quality 3

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 59.9/100 with 60.0% coverage. It contains 118 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in security (12), cicd (6), network (3). Risk profile is low: 0 critical, 0 high, 20 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 21 of 23 actionable findings. 26 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 quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

medium System graph hardware Supply chain conf 1.00 Docker base image uses a mutable or implicit tag: alpine:latest

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:10 containersPinned dependencies

medium System graph security Trivy conf 1.00 DS-0001: ':latest' tag used — Dockerfile

':latest' tag used Specify a tag in the 'FROM' statement for image 'alpine' Rule: DS-0001 Severity: MEDIUM Target: Dockerfile

Misconfig

medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

3 files, 3 locations

.github/workflows/deploy.yml:13

.github/workflows/release.yml:16

.github/workflows/winget.yml:14

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 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 security Semgrep conf 1.00 potential dos via decompression bomb — src/compress/compress.go:49

Detected a possible denial-of-service via a zip bomb attack. By limiting the max bytes read, you can mitigate this attack. `io.CopyN()` can specify a size. Rule: go.lang.security.decompression_bomb.potential-dos-via-decompression-bomb Severity: WARNING OWASP: — CWE: CWE-400: Uncontrolled Resource …

SecurityGo

medium System graph security Semgrep conf 1.00 potential dos via decompression bomb — src/utils/utils.go:820

SecurityGo

medium System graph network Security conf 1.00 Privileged port 32 in use

Port 32 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

.goreleaser.yml Ports

medium System graph network Security conf 1.00 Privileged port 386 in use

Port 386 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

.goreleaser.yml Ports

medium System graph network Security conf 1.00 Privileged port 64 in use

Port 64 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

.goreleaser.yml Ports

medium System graph security Semgrep conf 1.00 use of md5 — src/utils/ctx.go:213

Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. Rule: go.lang.security.audit.crypto.use_of_weak_crypto.use-of-md5 Severity: WARNING OWASP: A03:2017 - Sensitive Data Expo…

SecurityGo

medium System graph security Semgrep conf 1.00 use of md5 — src/utils/utils.go:183

SecurityGo

medium System graph security Semgrep conf 1.00 use of unsafe block — src/diskusage/diskusage_windows.go:24

Using the unsafe package in Go gives you low-level memory management and many of the strengths of the C language, but also steps around the type safety of Go and can lead to buffer overflows and possible arbitrary code execution by an attacker. Only use this package if you absolutely know what you'…

SecurityGo

medium System graph security Semgrep conf 1.00 use of unsafe block — src/diskusage/diskusage_windows.go:25

SecurityGo

medium System graph security Semgrep conf 1.00 use of unsafe block — src/diskusage/diskusage_windows.go:26

SecurityGo

medium System graph security Semgrep conf 1.00 use of unsafe block — src/diskusage/diskusage_windows.go:27

SecurityGo

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.25-alpine

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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 2 locations

.github/workflows/ci.yml:14

.github/workflows/stale.yml:16

CI/CD securitySupply chainGithub actions

low System graph quality Complexity conf 1.00 Very large file: src/croc/croc.go (3031 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: src/croc/croc_test.go (2336 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/d1cdc690-a6a0-46b0-b14b-1d4764b72da6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d1cdc690-a6a0-46b0-b14b-1d4764b72da6/

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.