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

thewoolleyman/livespec-dev-tooling

https://github.com/thewoolleyman/livespec-dev-tooling · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

145 raw signals (0 security + 145 graph)

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

Complete repo analysis

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

JSON
Combined
64.0
/100
Security checks
64
0 findings
System graph
64
77.8% cov · 87 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 27 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 87 Crowd 0 Layer: Software 8 Hardware 4 Frontend 1 Security 1 Cicd 3 Quality 70
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.0/100 with 77.8% coverage. It contains 2304 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 145 findings — concentrated in quality (86), cicd (45), software (8). Risk profile is high: 0 critical, 1 high, 44 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 37 of 87 actionable findings. 145 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.
docker/fabro-sandbox/Dockerfile:51 containersRemote installer
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: dev-tooling/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
dev-tooling/CLAUDE.md VerificationClaude instruction
medium System graph hardware Security conf 1.00 Dockerfile runs as root: docker/fabro-sandbox/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 16 occurrences GitHub Action is tag-pinned rather than SHA-pinned
thewoolleyman/livespec-dev-tooling/.github/workflows/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
10 files, 16 locations
.github/workflows/fabro-sandbox-image.yml:69, 73, 85, 95 (4 hits)
.github/workflows/ci.yml:96, 130, 209 (3 hits)
.github/workflows/reusable-pin-freshness.yml:97, 201 (2 hits)
.github/workflows/bump-pin-from-dispatch.yml:27
.github/workflows/fleet-conformance.yml:42
.github/workflows/pin-freshness.yml:28
.github/workflows/release-dispatch.yml:24
.github/workflows/release-please.yml:65
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences 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.
3 files, 3 locations
.github/workflows/auto-update-branches.yml
.github/workflows/fabro-sandbox-image.yml
.github/workflows/release-please.yml
CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/agent_hooks/subagent_stop_guard.py:105
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/_red_green_replay_modes.py:78
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/branch_protection_alignment.py:173
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/check_coverage_incremental.py:228
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/check_mutation.py:240
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/check_tools.py:82
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/commit_pairs_source_and_test.py:77
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/master_ci_green.py:82
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/primary_checkout_commit_refuse_hook_installed.py:127
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/red_green_replay.py:161
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/checks/tests_no_subprocess_spawn.py:99
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/fleet/_context.py:110
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/green_token.py:47
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/parallel_check_dispatcher.py:223
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/red_leg_scope.py:142
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/tdd_commit.py:176
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/testing/cli_e2e.py:239
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — livespec_dev_tooling/workflow_checks/no_stale_revise_branches.py:164
`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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 18 placeholder/mock markers across 5 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: buildpack-deps:noble
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
docker/fabro-sandbox/Dockerfile:29 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 26 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/create-github-app-token@v1 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
10 files, 26 locations
.github/workflows/reusable-pin-freshness.yml:81, 87, 90, 182, 188, 194 (6 hits)
.github/workflows/ci.yml:39, 92, 119, 123, 177 (5 hits)
.github/workflows/reusable-release-dispatch.yml:98, 139, 149, 179 (4 hits)
.github/workflows/reusable-bump-pin-from-dispatch.yml:98, 104, 148 (3 hits)
.github/workflows/fleet-conformance.yml:31, 35 (2 hits)
.github/workflows/reusable-check-matrix.yml:49, 52 (2 hits)
.github/workflows/auto-enable-merge.yml:86
.github/workflows/auto-update-branches.yml:69
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 15 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: livespec_dev_tooling/_vendor/structlog/stdlib.py:findCaller, livespec_dev_tooling/_vendor/structlog/stdlib.py:findCaller This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or…
15 occurrences
repo-level (15 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: livespec_dev_tooling/_vendor/structlog/_base.py:unbind, livespec_dev_tooling/_vendor/structlog/stdlib.py:unbind, livespec_dev_tooling/_vendor/structlog/stdlib.py:unbind This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — se…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 38 places
Functions with the same first-5-line body hash: livespec_dev_tooling/fabro_image_pin_lockstep.py:main, livespec_dev_tooling/green_token.py:main, livespec_dev_tooling/fleet/fleet_conformance.py:main, livespec_dev_tooling/fleet/wire_fleet_member.py:main This is *the* AI-coder failure mode (4× more d…
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: livespec_dev_tooling/_vendor/structlog/stdlib.py:critical, livespec_dev_tooling/_vendor/structlog/stdlib.py:fatal, livespec_dev_tooling/_vendor/structlog/stdlib.py:critical, livespec_dev_tooling/_vendor/structlog/stdlib.py:fatal This is *the* AI-code…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_impl_plugin_consumes_check_without_local_copy` in tests/consumer/test_package_consumption.py:101
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_old` in tests/livespec_dev_tooling/checks/test_heading_coverage.py:129
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 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 Integrity conf 1.00 Stub function `_nop` (body is just `pass`/`return`) — livespec_dev_tooling/_vendor/structlog/_native.py:34
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Complexity conf 1.00 Very large file: tests/livespec_dev_tooling/checks/test_red_green_replay.py (2532 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/67bfc7b7-b1c9-4344-97ef-5420d01dd278/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/67bfc7b7-b1c9-4344-97ef-5420d01dd278/

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.