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.

yonatangross/orchestkit

https://github.com/yonatangross/orchestkit · scanned 2026-06-16 01:09 UTC (2 months, 1 week ago)

663 raw signals (0 security + 663 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 636 actionable findings from 1 signal source. 27 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 · 636 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 66 Medium 360 Low 96 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 636 Crowd 0 Layer: Software 25 Frontend 49 Network 10 Security 352 Cicd 3 Quality 170 Api 27

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Commented-out code 106 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (8 lines) in tests/manifests/test-skill-activation-channel…
info Commented-code block (6 lines) in docs/site/middleware.ts:9
info Commented-code block (5 lines) in docs/site/__tests__/contextual-skill-sidebar.…
info Commented-code block (8 lines) in docs/site/__tests__/search-indexes.test.ts:6
info Commented-code block (5 lines) in docs/site/__tests__/sitemap.test.ts:9
info Commented-code block (5 lines) in docs/site/components/agent-readiness-section.…
info Commented-code block (5 lines) in docs/site/components/content-page.tsx:9
info Commented-code block (6 lines) in docs/site/components/structured-data.tsx:3
info Commented-code block (6 lines) in docs/site/app/robots.txt/route.ts:3
info Commented-code block (5 lines) in docs/site/app/api/route.ts:3
info Commented-code block (6 lines) in docs/site/app/api/md/[[...slug]]/route.ts:8
info Commented-code block (5 lines) in docs/site/app/api/mcp/route.ts:5

View all commented-out code findings →

Config drift 35 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

medium Insecure pattern 'direct_innerhtml_assignment' in docs/chore--configure-2176-se… docs/chore--configure-2176-settings/settings-cata…:46
high Agent instruction/config may expose a secret: docs/site/.claude/agent-memory/or… docs/site/.claude/agent-memory/ork-web-research-a…:11
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-und…:5
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13
high Agent instruction/config may expose a secret: src/hooks/.claude/orchestration/t… src/hooks/.claude/orchestration/task-registry-int…:13

View all config drift findings →

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/404255ba-4592-4bbf-b1f6-edbfa194884c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/404255ba-4592-4bbf-b1f6-edbfa194884c/

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.