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.

rogers-group-inc/polaris

https://github.com/rogers-group-inc/polaris · scanned 2026-06-15 23:54 UTC (2 months, 3 weeks ago)

389 raw signals (44 security + 345 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 336 actionable findings from 2 signal sources. 93 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 · 327 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 28 Medium 82 Low 96 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 327 Crowd 0 Layer: Quality 180 Security 59 Frontend 11 Network 6 Hardware 4 Cicd 4 Api 72

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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `_amonCoerceLegacy` in public/js/integrations.js:14…

View all legacy markers findings →

Commented-out code 124 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 demo.mjs:588
info Commented-code block (5 lines) in tests/integration/monitorSettings.test.ts:309
info Commented-code block (6 lines) in tests/integration/assetMerge.test.ts:50
info Commented-code block (6 lines) in tests/unit/extractHaFromFmgDevice.test.ts:129
info Commented-code block (6 lines) in tests/unit/fmgRpcRetry.test.ts:4
info Commented-code block (6 lines) in tests/unit/timescaleTables.test.ts:81
info Commented-code block (6 lines) in tests/unit/capacityAdvisorService.test.ts:434
info Commented-code block (5 lines) in tests/unit/fortinetSerialPattern.test.ts:58
info Commented-code block (6 lines) in tests/unit/dependencyTreeService.test.ts:229
info Commented-code block (5 lines) in tests/unit/stdMibLibrary.test.ts:19
info Commented-code block (5 lines) in tests/unit/extractMetavarCoordsFromFmgDevice.…
info Commented-code block (10 lines) in scripts/check-docs.mjs:13

View all commented-out code findings →

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

5 matching findings on this repo

high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:236
high Dangling fetch: GET /api/v1/auth/azure/config (public/js/login.js:46)
high Dangling fetch: GET /api/v1/auth/oidc/config (public/js/login.js:73)
high Dangling fetch: GET /api/v1/auth/azure/config (public/js/mobile/auth.js:22)
low Unused endpoint: GET /azure/config

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/87ab2f94-42b7-4da8-8094-d6905592c895/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/87ab2f94-42b7-4da8-8094-d6905592c895/

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.