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.

byungjunjang/slide-html

https://github.com/byungjunjang/slide-html · scanned 2026-06-17 01:44 UTC (1 month, 2 weeks ago)

90 raw signals (0 security + 90 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -28.7 (diff) · 71 actionable findings from 1 signal source. 19 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

44.4% cov · 71 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 28 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 71 Crowd 0 Layer: Software 10 Frontend 2 Security 6 Quality 53

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 →

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

high Agent instruction/config may expose a secret: .codex/skills/theme-init/referenc… .codex/skills/theme-init/references/legacy-migrat…:57
high Agent instruction/config may expose a secret: .claude/skills/theme-init/referen… .claude/skills/theme-init/references/legacy-migra…:57

View all legacy markers findings →

Commented-out code 12 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 (6 lines) in .codex/skills/slide/scripts/html2pptx.js:32
info Commented-code block (6 lines) in .codex/skills/slide/scripts/render-diagram.mj…
info Commented-code block (5 lines) in .codex/skills/slide/scripts/prebuild-svg.mjs:3
info Commented-code block (5 lines) in .codex/skills/slide/scripts/dev/sync_codex_mi…
info Commented-code block (5 lines) in .codex/skills/theme-init/scripts/migrate_patt…
info Commented-code block (5 lines) in .codex/skills/theme-init/scripts/init_theme.p…
info Commented-code block (6 lines) in .claude/skills/slide/scripts/html2pptx.js:32
info Commented-code block (6 lines) in .claude/skills/slide/scripts/render-diagram.m…
info Commented-code block (5 lines) in .claude/skills/slide/scripts/prebuild-svg.mjs…
info Commented-code block (5 lines) in .claude/skills/slide/scripts/dev/sync_codex_m…
info Commented-code block (5 lines) in .claude/skills/theme-init/scripts/migrate_pat…
info Commented-code block (5 lines) in .claude/skills/theme-init/scripts/init_theme.…

View all commented-out code findings →

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

2 matching findings on this repo

high Agent instruction/config may expose a secret: .codex/skills/theme-init/referenc… .codex/skills/theme-init/references/legacy-migrat…:57
high Agent instruction/config may expose a secret: .claude/skills/theme-init/referen… .claude/skills/theme-init/references/legacy-migra…:57

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/41a2fafa-4987-49f0-bbb1-70ececb11823/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/41a2fafa-4987-49f0-bbb1-70ececb11823/

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.