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

Query-farm-haybarn/haybarn-extension-ci-tools

https://github.com/Query-farm-haybarn/haybarn-extension-ci-tools · scanned 2026-06-15 23:43 UTC (2 months, 4 weeks ago)

50 raw signals (0 security + 50 graph)

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

Complete repo analysis

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

JSON
Combined
57.1
/100
Security checks
57
0 findings
System graph
57
77.8% cov · 32 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 14 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 32 Crowd 0 Layer: Software 1 Network 1 Hardware 11 Frontend 1 Security 2 Cicd 5 Quality 11
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 57.1/100 with 77.8% coverage. It contains 143 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 50 findings — concentrated in cicd (23), hardware (11), quality (11). Risk profile is high: 0 critical, 3 high, 20 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 26 of 32 actionable findings. 50 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 cicd CI/CD security conf 1.00 3 occurrences GitHub Action tracks a moving branch
hendrikmuhs/ccache-action@main can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 868, 1251, 1648
.github/workflows/_extension_distribution.yml:868, 1251, 1648 (3 hits)
CI/CD securitySupply chainGithub actions
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 Security conf 1.00 Dockerfile runs as root: docker/linux_amd64/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/linux_amd64_musl/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/linux_arm64/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/linux_arm64_musl/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/wasm/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 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned
endersonmenezes/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 7 locations
.github/workflows/_extension_distribution.yml:369, 1223, 1227, 1351, 1621 (5 hits)
.github/workflows/publish-build-images.yml:100, 212 (2 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/publish-build-images.yml 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/_extension_registry_publish.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in scripts/publish/generate_haybarn_metadata.py:70
Found a known-risky pattern (weak_hash). Review and replace if possible.
scripts/publish/generate_haybarn_metadata.py:70 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in scripts/publish/r2_build_manifest.py:109
Found a known-risky pattern (weak_hash). Review and replace if possible.
scripts/publish/r2_build_manifest.py:109 Weak hash
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/publish/publish_extensions.py:131
`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 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.
docker/linux_arm64/Dockerfile Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 11 source file(s) (ratio 0.00). 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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 52 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: alpine:3.22
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/linux_amd64_musl/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.22
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/linux_arm64_musl/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: quay.io/pypa/manylinux_2_28_aarch64:2026.05.13-1
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/linux_arm64/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: quay.io/pypa/manylinux_2_28_x86_64:2026.05.13-1
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/linux_amd64/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ubuntu:24.04
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/wasm/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 11 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, 11 locations
.github/workflows/_extension_distribution.yml:485, 898, 949, 1233, 1314, 1586, 1627 (7 hits)
.github/workflows/_extension_registry_publish.yml:129, 138, 194, 285 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/publish/npm_build_meta.py:main, scripts/publish/npm_build_leaf.py:main 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.
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: process_tuple
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/publish/publish_extensions.py:436
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/c4dd54a8-3ddd-4d80-ad98-bfa808508801/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c4dd54a8-3ddd-4d80-ad98-bfa808508801/

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.