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.

zachsrosen/pb-operations-suite

https://github.com/zachsrosen/pb-operations-suite · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

1001 raw signals (0 security + 1001 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 994 actionable findings from 1 signal source. 7 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 · 994 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 362 Low 375 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 994 Crowd 0 Layer: Api 1 Frontend 469 Hardware 3 Security 17 Cicd 2 Quality 502

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

6 matching findings on this repo

low Very large file: src/app/dashboards/pe/legacy/page.tsx (1425 lines)
low Old/deprecated-named symbol `obviousLegacy` in scripts/_export-hubspot-orphan-l…
low Old/deprecated-named symbol `hsLegacy` in scripts/list-all-gaps-with-dupes.ts:1…
low Old/deprecated-named symbol `showLegacy` in src/app/admin/roles/page.tsx:119
low Old/deprecated-named symbol `isLegacy` in src/app/admin/roles/_RoleDrawerBody.t…
low Old/deprecated-named symbol `syncWithDirectInsertLegacy` in src/lib/bom-snapsho…

View all legacy markers findings →

Commented-out code 101 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 next.config.ts:28
info Commented-code block (5 lines) in scripts/create-hubspot-property-object.ts:1
info Commented-code block (5 lines) in scripts/backfill-zuper-properties.ts:6
info Commented-code block (5 lines) in scripts/pe-photo-submit.ts:84
info Commented-code block (5 lines) in scripts/backfill-properties.ts:18
info Commented-code block (9 lines) in scripts/cleanup-bare-property-dupes.ts:11
info Commented-code block (8 lines) in src/middleware.ts:235
info Commented-code block (6 lines) in src/__tests__/zuper-status-mapping.test.ts:69
info Commented-code block (5 lines) in src/__tests__/adders/seed-integrity.test.ts:1
info Commented-code block (5 lines) in src/__tests__/lib/property-sync.test.ts:1163
info Commented-code block (5 lines) in src/__tests__/lib/user-access.test.ts:228
info Commented-code block (7 lines) in src/__tests__/lib/property-backfill-lock.test…

View all commented-out code findings →

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

3 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/seed-ooo-bot-config.ts:53
info Commented-code block (5 lines) in next.config.ts:28
medium `fetch()` without try/.catch or AbortSignal — src/components/on-call/PoolConfig…

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/f485f31d-ff19-4b3a-9f27-8ea86604cfe8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f485f31d-ff19-4b3a-9f27-8ea86604cfe8/

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.