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.

stdray/petbox

https://github.com/stdray/petbox · scanned 2026-06-16 00:21 UTC (2 months, 2 weeks ago)

59 raw signals (0 security + 59 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 44 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

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 72.2/100 with 100.0% coverage. It contains 1193 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 59 findings — concentrated in quality (30), cicd (11), hardware (5). Risk profile is high: 0 critical, 1 high, 18 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 35 of 44 actionable findings. 59 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:6 containersRemote installer

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/clients-ts/petbox-client/src/client.ts:94

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/clients-ts/petbox-client/src/data.ts:64

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/PetBox.Web/ts/config.ts:31

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/PetBox.Web/ts/workspace.ts:50

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

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

docker/setup-buildx-action@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 91, 94, 126

.github/workflows/ci.yml:91, 94, 126 (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/ci.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/PetBox.Web/ts/logs.ts:144

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

src/PetBox.Web/ts/logs.ts:144 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/PetBox.Web/ts/markdown.ts:20

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

src/PetBox.Web/ts/markdown.ts:20 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/PetBox.Web/ts/nodeEdit.ts:40

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

src/PetBox.Web/ts/nodeEdit.ts:40 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in agents/wiring/wire.ts:18

Found a known-risky pattern (node_child_process). Review and replace if possible.

agents/wiring/wire.ts:18 Node child process

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — agent/petbox_deploy_agent.py:93

`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 — eval/search/fetch_locomo.py:20

`urllib.request.urlretrieve(...)` 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

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 71 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: mcr.microsoft.com/dotnet/nightly/runtime-deps:10.0-noble-chiseled

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

Dockerfile:46 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/dotnet/sdk:10.0

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 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned

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

lines 43, 53, 84, 211, 226, 253, 282

.github/workflows/ci.yml:43, 53, 84, 211, 226, 253, 282 (7 hits)

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 7 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: eval/search/eval_digest_strategy.py:deepseek, eval/search/eval_kscale.py:deepseek 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 2 occurrences Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: eval/search/eval_locomo_sem.py:build_match, eval/search/eval_digest_strategy.py:build_match, eval/search/eval_digest_models.py:build_match, eval/search/eval_hydration.py:build_match This is *the* AI-coder failure mode (4× more duplication in vibe-cod…

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 `cleanupLegacy` in agents/wiring/wire.ts:35

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: apply_schema

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

src/clients-py/petbox-client/src/petbox_client/data.py:137

low System graph software Dead code conf 1.00 Possibly dead Python function: chat_qwen

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

eval/search/eval_digest_models.py:70

low System graph software Dead code conf 1.00 Possibly dead Python function: off

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

src/clients-py/petbox-client/src/petbox_client/client.py:95

low System graph software Dead code conf 1.00 Possibly dead Python function: work

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

eval/search/eval_kscale.py:48

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 — agents/wiring/import-sessions.ts:202

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

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — agents/wiring/wire.ts:68

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

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/clients-ts/petbox-client/src/client.ts:28

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/e33e236e-4025-4c13-93b4-a145d4767c00/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e33e236e-4025-4c13-93b4-a145d4767c00/

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.