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.

dether-net/dethernety-oss

https://github.com/dether-net/dethernety-oss · scanned 2026-06-17 01:55 UTC (1 month, 1 week ago)

191 raw signals (0 security + 191 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 28 Low 54 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 180 Crowd 0 Layer: Software 5 Frontend 21 Security 10 Cicd 4 Quality 135 Api 5

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 2 findings

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.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

low Old/deprecated-named symbol `resetModuleLegacy` in apps/dt-ws/src/gql/resolver-…
low Old/deprecated-named symbol `getModuleTemplateLegacy` in apps/dt-ws/src/gql/res…

View all legacy markers findings →

Commented-out code 97 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/dt-core/src/dt-class-identity/__test…
info Commented-code block (6 lines) in packages/dt-core/src/dt-model/dt-model.ts:394
info Commented-code block (5 lines) in packages/dt-core/src/dt-control/dt-control.ts…
info Commented-code block (8 lines) in packages/dt-core/src/dt-class/dt-class.ts:349
info Commented-code block (12 lines) in packages/dt-core/src/dt-issue/dt-issue.ts:337
info Commented-code block (8 lines) in packages/dt-core/src/dt-analysis/dt-analysis-…
info Commented-code block (5 lines) in packages/dt-core/src/dt-component/dt-componen…
info Commented-code block (6 lines) in packages/dt-core/src/dt-exposure/dt-exposure-…
info Commented-code block (7 lines) in packages/dt-core/src/interfaces/core-types-in…
info Commented-code block (5 lines) in packages/dt-core/src/dt-import/dt-import.ts:9…
info Commented-code block (11 lines) in packages/dt-core/src/dt-control-library/audi…
info Commented-code block (5 lines) in packages/dt-core/src/dt-control-library/wal-h…

View all commented-out code findings →

Config drift 4 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.

4 matching findings on this repo

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: apps/dethereal/skills/enrich/SKIL… apps/dethereal/skills/enrich/SKILL.md:409
info Commented-code block (5 lines) in modules/dethernety-threat-report/vitest.confi…
info Commented-code block (6 lines) in apps/dt-ui/src/config/environment-todo.ts:260

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/8cf0d526-3dca-4d8f-b08d-dadce0a27073/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8cf0d526-3dca-4d8f-b08d-dadce0a27073/

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.