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.

avisangle/avisangle.github.io

https://github.com/avisangle/avisangle.github.io · scanned 2026-06-17 01:36 UTC (1 month, 2 weeks ago)

120 raw signals (0 security + 120 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 119 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 5 Medium 87 Low 23 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 119 Crowd 0 Layer: Software 4 Frontend 35 Security 47 Quality 33

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 →

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (9 lines) in next.config.ts:129

View all commented-out code findings →

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

6 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/blog-guidelines.md .claude/blog-guidelines.md:270
high Agent instruction/config may expose a secret: .claude/content-briefs/ant-cli-ge… .claude/content-briefs/ant-cli-getting-started.md:194
high Agent instruction/config may expose a secret: .claude/content-briefs/claude-man… .claude/content-briefs/claude-managed-agents.md:191
high Agent instruction/config may expose a secret: .claude/content-briefs/mcp-code-e… .claude/content-briefs/mcp-code-execution-pattern…:244
high Agent instruction/config may expose a secret: .claude/content-briefs/regression… .claude/content-briefs/regression-proofing-claude…:178
info Commented-code block (9 lines) in next.config.ts:129

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/e5f5df94-6fca-4cfc-947f-dcea125221fa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e5f5df94-6fca-4cfc-947f-dcea125221fa/

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.