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.

rahmanef63/resource-site

https://github.com/rahmanef63/resource-site · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

730 raw signals (36 security + 694 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 689 actionable findings from 2 signal sources. 112 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 · 681 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 6 Medium 75 Low 75 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 681 Crowd 0 Layer: Quality 273 Security 36 Frontend 375 Hardware 3 Cicd 2

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.

Legacy markers 3 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.

3 matching findings on this repo

low Old/deprecated-named symbol `hasLegacy` in frontend/slices/notion/slices/editor…
low Old/deprecated-named symbol `studioFlowToLegacy` in template-base/frontend/slic…
low Old/deprecated-named symbol `studioFlowToLegacy` in template-base/frontend/slic…

View all legacy markers findings →

Commented-out code 216 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 next.config.mjs:119
info Commented-code block (6 lines) in proxy.ts:10
info Commented-code block (13 lines) in frontend/slices/file-explorer/adapter/live.t…
info Commented-code block (5 lines) in frontend/slices/file-explorer/adapter/types.t…
info Commented-code block (10 lines) in frontend/slices/file-explorer/adapter/convex…
info Commented-code block (7 lines) in frontend/slices/file-explorer/lib/backend.ts:6
info Commented-code block (5 lines) in frontend/slices/file-explorer/lib/read-drop.t…
info Commented-code block (5 lines) in frontend/slices/file-explorer/hooks/use-dnd.t…
info Commented-code block (5 lines) in frontend/slices/user-management/components/Me…
info Commented-code block (5 lines) in frontend/slices/user-management/lib/tools.ts:1
info Commented-code block (10 lines) in frontend/slices/create-your-mcp/index.ts:5
info Commented-code block (7 lines) in frontend/slices/create-your-mcp/routes/oauth-…

View all commented-out code findings →

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

7 matching findings on this repo

info TODO/FIXME marker in shipping code — template-base/frontend/shared/communicatio…
info `truncate` class without `title=` for hover reveal — components/templates/_shar…
medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in next.config.mjs:119
info Commented-code block (5 lines) in frontend/slices/appshell/registry/shell-confi…
info Commented-code block (5 lines) in components/templates/kreator-studio/shared/na…
info Commented-code block (5 lines) in components/templates/_shared/config/template-…

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/452b8fa7-5b52-404f-bee8-b756413d47da/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/452b8fa7-5b52-404f-bee8-b756413d47da/

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.