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/template-riset-kit

https://github.com/rahmanef63/template-riset-kit · scanned 2026-06-15 23:45 UTC (2 months, 4 weeks ago)

80 raw signals (0 security + 80 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 80 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 80 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 12 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 80 Crowd 0 Layer: Api 1 Frontend 51 Security 5 Cicd 1 Quality 22

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.

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 (5 lines) in frontend/slices/icon-picker/lib/picker-handle…
info Commented-code block (8 lines) in frontend/slices/notion-shell/index.ts:19
info Commented-code block (5 lines) in frontend/slices/notion-database/components/ce…
info Commented-code block (5 lines) in frontend/slices/onboarding-wizard/components/…
info Commented-code block (5 lines) in scripts/setup-auth.mjs:1
info Commented-code block (5 lines) in components/templates/_shared/config/template-…
info Commented-code block (10 lines) in components/templates/_shared/admin-panel/ui/…
info Commented-code block (5 lines) in components/templates/_shared/admin-panel/bloc…
info Commented-code block (5 lines) in components/onboarding/onboarding-wizard.tsx:3
info Commented-code block (7 lines) in convex/auth.ts:5
info Commented-code block (5 lines) in convex/update.ts:6
info Commented-code block (5 lines) in lib/stage.ts:3

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

info `truncate` class without `title=` for hover reveal — components/templates/_shar…
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/48c27995-d055-4776-866d-1d7e353ca26f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/48c27995-d055-4776-866d-1d7e353ca26f/

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.