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.

dork-labs/dorkos

https://github.com/dork-labs/dorkos · scanned 2026-06-17 02:01 UTC (1 month, 1 week ago)

438 raw signals (0 security + 438 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -33.5 (diff) · 429 actionable findings from 1 signal source. 9 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 · 429 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 29 Medium 101 Low 122 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 429 Crowd 0 Layer: Software 1 Frontend 125 Hardware 2 Security 42 Cicd 5 Quality 181 Api 73

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

View all duplicates & near-duplicates findings →

Commented-out code 92 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 (5 lines) in packages/test-utils/src/mock-factories.ts:150
info Commented-code block (6 lines) in packages/relay/src/adapters/claude-code/claud…
info Commented-code block (7 lines) in packages/relay/src/adapters/claude-code/__tes…
info Commented-code block (6 lines) in packages/relay/src/adapters/telegram/__tests_…
info Commented-code block (5 lines) in packages/relay/src/adapters/slack/outbound.ts…
info Commented-code block (7 lines) in packages/relay/src/__tests__/relay-core.test.…
info Commented-code block (11 lines) in packages/db/src/schema/sessions.ts:3
info Commented-code block (5 lines) in packages/cli/src/cli.ts:59
info Commented-code block (5 lines) in packages/cli/src/commands/package-validate-re…
info Commented-code block (6 lines) in packages/cli/src/commands/package-validate-ma…
info Commented-code block (5 lines) in packages/cli/src/__tests__/cache-commands.tes…
info Commented-code block (7 lines) in packages/shared/src/session-stream.ts:232

View all commented-out code findings →

Config drift 14 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

low Stray `console.log` in TS/JS — packages/cli/src/config-commands.ts:78
info `truncate` class without `title=` for hover reveal — apps/client/src/layers/fea…
info `truncate` class without `title=` for hover reveal — apps/client/src/layers/fea…
info `truncate` class without `title=` for hover reveal — apps/client/src/layers/fea…
medium Insecure pattern 'node_child_process' in packages/cli/src/config-commands.ts:3 packages/cli/src/config-commands.ts:3
critical Possible secret in apps/server/src/routes/__tests__/config-mcp.test.ts apps/server/src/routes/__tests__/config-mcp.test.…:130
low Node manifest has dependencies but no lockfile: packages/eslint-config/package.… packages/eslint-config/package.json
high Agent instruction/config may expose a secret: .claude/agents/research-expert.md .claude/agents/research-expert.md:60
high Agent instruction/config may expose a secret: .claude/agents/react/react-tansta… .claude/agents/react/react-tanstack-expert.md:338
high Agent instruction/config may expose a secret: .claude/commands/system/release.md .claude/commands/system/release.md:754
info Commented-code block (6 lines) in apps/server/src/services/core/config-manager.…
info Commented-code block (6 lines) in apps/client/src/layers/features/status/__test…

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/50013d13-2b13-45b6-b039-688162b7d0d0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/50013d13-2b13-45b6-b039-688162b7d0d0/

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.