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.

skoigi2/property-manager

https://github.com/skoigi2/property-manager · scanned 2026-06-16 00:15 UTC (2 months, 2 weeks ago)

150 raw signals (15 security + 135 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 142 actionable findings from 2 signal sources. 9 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 · 135 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 4 Medium 52 Low 31 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 135 Crowd 0 Layer: Quality 79 Security 7 Api 1 Frontend 55

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 (6 lines) in scripts/backfill-property-access.ts:4
info Commented-code block (14 lines) in scripts/wipe-property-expenses.ts:5
info Commented-code block (5 lines) in src/app/api/demo/seed/route.ts:3328
info Commented-code block (5 lines) in src/app/api/users/route.ts:162
info Commented-code block (5 lines) in src/app/api/invoices/[id]/route.ts:76
info Commented-code block (5 lines) in src/app/(dashboard)/tenants/page.tsx:71
info Commented-code block (6 lines) in src/lib/auth-utils.ts:91
info Commented-code block (6 lines) in src/lib/paddle.ts:3
info Commented-code block (6 lines) in src/lib/prisma-decimal-extension.ts:1
info Commented-code block (6 lines) in src/lib/automation-registry.ts:4
info Commented-code block (5 lines) in src/lib/rental-calculator.ts:168
info Commented-code block (6 lines) in src/lib/prisma.ts:5

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 — src/components/settings/Ta…
high Agent instruction/config may expose a secret: .claude/settings.local.json .claude/settings.local.json:23

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/a6c33717-18b3-45f2-8e95-532359ddea40/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a6c33717-18b3-45f2-8e95-532359ddea40/

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.