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.
Sign up free Scan another repo

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
Combined
39.9
/100
Security checks
40
9 findings
System graph
40
100.0% cov · 327 findings
Critical
5
click to filter
Agents
10
0 votes
Crowd
0
reported
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
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 39.9/100 with 100.0% coverage. It contains 5487 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 345 findings — concentrated in quality (172), api (72), security (68). Risk profile is high: 13 critical, 24 high, 82 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 211 of 336 actionable findings. 429 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical Security checks quality Practices conf 0.82 2 occurrences Foundry mined mock as real or placeholder: rogers-group-inc/polaris
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
2 occurrences
repo-level (2 hits)
critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: rogers-group-inc/polaris
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
critical System graph security Secrets conf 1.00 9 occurrences Possible secret in demo.mjs
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 831, 1044, 4036, 4189, 4199, 4262, 4323, 4330, +1 more
demo.mjs:831, 1044, 4036, 4189, 4199, 4262, 4323, 4330, +1 more (9 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/api/routes/events.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 225, 240
src/api/routes/events.ts:225, 240 (2 hits)
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/api/routes/integrations.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 7824, 7830
src/api/routes/integrations.ts:7824, 7830 (2 hits)
high Security checks quality Practices conf 0.84 4 occurrences Foundry mined bad chains: rogers-group-inc/polaris
Comment chain pattern product: bad_chains Repo: rogers-group-inc/polaris Thread: rogers-group-inc/polaris#42 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, …
4 occurrences
repo-level (4 hits)
high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: rogers-group-inc/polaris
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: supported_by_ve…
high Security checks quality Quality conf 0.76 11 occurrences Foundry mined schema ui api mismatch: rogers-group-inc/polaris
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…
11 occurrences
repo-level (11 hits)
high Security checks quality Testing conf 0.78 8 occurrences Foundry mined test ci gap after feedback: rogers-group-inc/polaris
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: weak_supervision_needs_…
8 occurrences
repo-level (8 hits)
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
CLAUDE.md:236 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/setup/status (public/js/login.js:88)
`public/js/login.js:88` calls `GET /api/setup/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/setup/status` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/setup/status (public/js/setup.js:12)
`public/js/setup.js:12` calls `GET /api/setup/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/setup/status` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/azure/config (public/js/login.js:46)
`public/js/login.js:46` calls `GET /api/v1/auth/azure/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/azure/config` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/azure/config (public/js/mobile/auth.js:22)
`public/js/mobile/auth.js:22` calls `GET /api/v1/auth/azure/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/azure/config` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me (public/js/app.js:62)
`public/js/app.js:62` calls `GET /api/v1/auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me (public/js/mobile/app.js:63)
`public/js/mobile/app.js:63` calls `GET /api/v1/auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/me (public/js/mobile/more-tab.js:262)
`public/js/mobile/more-tab.js:262` calls `GET /api/v1/auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/me` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/auth/oidc/config (public/js/login.js:73)
`public/js/login.js:73` calls `GET /api/v1/auth/oidc/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/oidc/config` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/server-settings/branding (public/js/login.js:24)
`public/js/login.js:24` calls `GET /api/v1/server-settings/branding` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/server-settings/branding` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/server-settings/branding (public/js/mobile/auth.js:64)
`public/js/mobile/auth.js:64` calls `GET /api/v1/server-settings/branding` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/server-settings/branding` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${path} (tests/unit/metricsServer.test.ts:15)
`tests/unit/metricsServer.test.ts:15` calls `GET http://127.0.0.1:${port}${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/setup/finalize (public/js/setup.js:306)
`public/js/setup.js:306` calls `POST /api/setup/finalize` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/setup/finalize` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/setup/generate-secret (public/js/setup.js:226)
`public/js/setup.js:226` calls `POST /api/setup/generate-secret` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/setup/generate-secret` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/setup/preflight (public/js/setup.js:128)
`public/js/setup.js:128` calls `POST /api/setup/preflight` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/setup/preflight` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/setup/test-connection (public/js/setup.js:83)
`public/js/setup.js:83` calls `POST /api/setup/test-connection` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/setup/test-connection` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/login (public/js/login.js:132)
`public/js/login.js:132` calls `POST /api/v1/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/login (public/js/mobile/auth.js:178)
`public/js/mobile/auth.js:178` calls `POST /api/v1/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/login/totp (public/js/login.js:193)
`public/js/login.js:193` calls `POST /api/v1/auth/login/totp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/login/totp` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/login/totp (public/js/mobile/auth.js:208)
`public/js/mobile/auth.js:208` calls `POST /api/v1/auth/login/totp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/login/totp` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/logout (public/js/app.js:2023)
`public/js/app.js:2023` calls `POST /api/v1/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/logout (public/js/app.js:218)
`public/js/app.js:218` calls `POST /api/v1/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/logout (public/js/mobile/more-tab.js:258)
`public/js/mobile/more-tab.js:258` calls `POST /api/v1/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/services/queueService.ts:255
Found a known-risky pattern (exec_used). Review and replace if possible.
src/services/queueService.ts:255 Exec used
medium Security checks quality Practices conf 0.62 22 occurrences Foundry mined assumption checks: rogers-group-inc/polaris
Comment chain pattern product: assumption_checks Repo: rogers-group-inc/polaris Thread: rogers-group-inc/polaris#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifact…
22 occurrences
repo-level (22 hits)
medium Security checks quality maintenance conf 0.70 26 occurrences Foundry mined blueprint gap alignment: rogers-group-inc/polaris
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
26 occurrences
repo-level (26 hits)
medium Security checks quality Practices conf 0.70 9 occurrences Foundry mined unresolved feedback: rogers-group-inc/polaris
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
9 occurrences
repo-level (9 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/api.js:38
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/mobile/asset-detail.js:68
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/mobile/auth.js:64
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/mobile/more-tab.js:258
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/mobile/tabs.js:317
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/server-settings.js:6580
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/js/setup.js:306
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/fetch-std-mibs.mjs:32
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/api/middleware/permissions.ts:171
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/api/routes/auth.ts:629
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app.ts:341
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/services/fortigateService.ts:137
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/services/monitoringService.ts:2485
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/services/queueService.ts:276
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/setup-buildx-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 66, 69, 77, 89
.github/workflows/docker-publish.yml:66, 69, 77, 89 (4 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/docker-publish.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/agent-build.js:133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/agent-build.js:133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/app.js:163
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/app.js:163 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/assets.js:246
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/assets.js:246 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/block-panel.js:16
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/block-panel.js:16 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/blocks.js:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/blocks.js:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/dashboard.js:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/dashboard.js:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/events.js:194
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/events.js:194 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/integrations.js:189
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/integrations.js:189 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/ip-panel.js:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/ip-panel.js:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/ipam.js:58
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/ipam.js:58 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/login.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/login.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/map.js:210
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/map.js:210 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/app.js:56
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/app.js:56 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/asset-detail.js:138
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/asset-detail.js:138 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/assets-tab.js:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/assets-tab.js:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/auth.js:33
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/auth.js:33 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/details.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/details.js:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/map-tab.js:115
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/map-tab.js:115 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/more-tab.js:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/more-tab.js:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/reservations-tab.js:63
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/reservations-tab.js:63 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/subnet-detail.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/subnet-detail.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/tabs.js:34
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/tabs.js:34 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/mobile/topology-tab.js:95
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/mobile/topology-tab.js:95 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/server-settings.js:97
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/server-settings.js:97 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/setup.js:145
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/setup.js:145 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/subnets.js:205
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/subnets.js:205 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/table-sf.js:65
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/table-sf.js:65 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/users.js:142
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/users.js:142 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widget-library.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widget-library.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/assetTypes.js:14
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/assetTypes.js:14 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/blockUtilization.js:16
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/blockUtilization.js:16 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/capacityHealth.js:13
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/capacityHealth.js:13 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/conflictQueue.js:10
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/conflictQueue.js:10 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/discoveryActivity.js:17
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/discoveryActivity.js:17 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/monitorAlerts.js:128
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/monitorAlerts.js:128 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/recentEvents.js:12
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/recentEvents.js:12 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/recentReservations.js:17
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/recentReservations.js:17 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/widgets/staleReservations.js:9
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/widgets/staleReservations.js:9 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in public/js/app.js:23
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
public/js/app.js:23 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/js/users.js:1703
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/js/users.js:1703 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in demo.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
demo.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/api/routes/serverSettings.ts:8
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/api/routes/serverSettings.ts:8 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/agentBuildService.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/agentBuildService.ts:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/eventArchiveService.ts:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/eventArchiveService.ts:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/monitoringService.ts:27
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/monitoringService.ts:27 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/privilegedSysadmin.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/privilegedSysadmin.ts:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/updateService.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/updateService.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/setup/setupRoutes.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/setup/setupRoutes.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/icmpPing.ts:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/icmpPing.ts:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/utils/version.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/utils/version.ts:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in public/js/server-settings.js:5575
Found a known-risky pattern (weak_hash). Review and replace if possible.
public/js/server-settings.js:5575 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in src/services/credentialService.ts:25
Found a known-risky pattern (weak_hash). Review and replace if possible.
src/services/credentialService.ts:25 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in src/services/monitoringService.ts:2591
Found a known-risky pattern (weak_hash). Review and replace if possible.
src/services/monitoringService.ts:2591 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 287 placeholder/mock markers across 43 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 11 in use
Port 11 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/seed-topology-mock.ts Ports
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/seed-topology-mock.ts Ports
medium System graph network Security conf 1.00 Privileged port 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/seed-topology-mock.ts Ports
medium System graph network Security conf 1.00 Privileged port 514 in use
Port 514 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
demo.mjs Ports
medium System graph network Security conf 1.00 Privileged port 636 in use
Port 636 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
demo.mjs Ports
medium System graph network Security conf 1.00 Privileged port 853 in use
Port 853 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
src/services/dnsService.ts Ports
low System graph quality Integrity conf 1.00 23 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DATABASE_POOL_SIZE`, `GOTOOLCHAIN`, `HEALTH_TOKEN`, `KUBERNETES_SERVICE_HOST`, `METRICS_TOKEN`, `NODE_TLS_REJECT_UNAUTHORIZED`, `POLARIS_AGENT_KEEP_VERSIONS`, `POLARIS_AGENT_SAMPLE_LOG` + 15 more. Add them (with a placeholder/comment) to .env.exam…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 141 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:30 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 6 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 6 locations
.github/workflows/docker-publish.yml:23, 26, 55, 102 (4 hits)
.github/workflows/check-docs.yml:22, 25 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — public/js/assets.js:11564
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_amonCoerceLegacy` in public/js/integrations.js:1451
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_polaris_backup` in demo.mjs:4593
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `skip_backup` in src/api/routes/serverSettings.ts:1328
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `skip_backup` in src/services/updateService.ts:454
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `subnet_deprecated` in src/services/reservationService.ts:1019
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — public/js/topology-render.js:122
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — src/utils/assetTypes.ts:52
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — prisma/seed.ts:23
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/audit-multi-mac-assets.ts:63
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-fmg-tokens.ts:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/diagnose-dhcp-create-conflicts.ts:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seed-fortilink-demo.ts:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seed-topology-mock.ts:312
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/smoke-std-mibs.ts:56
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/setup/setupServer.ts:60
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /azure/config
`src/api/routes/auth.ts` declares `GET /azure/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /azure/login
`src/api/routes/auth.ts` declares `GET /azure/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /azure/settings
`src/api/routes/auth.ts` declares `GET /azure/settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /blocks.html
`src/app.ts` declares `GET /blocks.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /me
`src/api/routes/auth.ts` declares `GET /me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /server-settings/branding
`src/api/router.ts` declares `GET /server-settings/branding` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /subnets.html
`src/app.ts` declares `GET /subnets.html` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`src/api/middleware/validate.ts` declares `POST /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /azure/callback
`src/api/routes/auth.ts` declares `POST /azure/callback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /azure/logout
`src/api/routes/auth.ts` declares `POST /azure/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /azure/test
`src/api/routes/auth.ts` declares `POST /azure/test` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`src/api/routes/auth.ts` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login/totp
`src/api/routes/auth.ts` declares `POST /login/totp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /logout
`src/api/routes/auth.ts` declares `POST /logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /agents
`src/api/router.ts` declares `USE /agents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /agents/binary
`src/api/router.ts` declares `USE /agents/binary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /agents/enroll
`src/api/router.ts` declares `USE /agents/enroll` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /allocation-templates
`src/api/router.ts` declares `USE /allocation-templates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api
`src/app.ts` declares `USE /api` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api-tokens
`src/api/router.ts` declares `USE /api-tokens` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/v1
`src/app.ts` declares `USE /api/v1` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/v1/auth/azure/login
`src/app.ts` declares `USE /api/v1/auth/azure/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/v1/auth/login
`src/app.ts` declares `USE /api/v1/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /asset-types
`src/api/router.ts` declares `USE /asset-types` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /assets
`src/api/router.ts` declares `USE /assets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /auth
`src/api/router.ts` declares `USE /auth` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /blocks
`src/api/router.ts` declares `USE /blocks` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /conflicts
`src/api/router.ts` declares `USE /conflicts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /credentials
`src/api/router.ts` declares `USE /credentials` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /dashboard
`src/api/router.ts` declares `USE /dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /device-icons
`src/api/router.ts` declares `USE /device-icons` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /events
`src/api/router.ts` declares `USE /events` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /group-mappings
`src/api/router.ts` declares `USE /group-mappings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /integrations
`src/api/router.ts` declares `USE /integrations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /manufacturer-aliases
`src/api/router.ts` declares `USE /manufacturer-aliases` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /map
`src/api/router.ts` declares `USE /map` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /map/regions
`src/api/router.ts` declares `USE /map/regions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /me/dashboard
`src/api/router.ts` declares `USE /me/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /monitor-settings
`src/api/router.ts` declares `USE /monitor-settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /reservations
`src/api/router.ts` declares `USE /reservations` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /roles
`src/api/router.ts` declares `USE /roles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /search
`src/api/router.ts` declares `USE /search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /server-settings
`src/api/router.ts` declares `USE /server-settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /server-settings/manufacturer-profiles
`src/api/router.ts` declares `USE /server-settings/manufacturer-profiles` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /server-settings/mibs
`src/api/router.ts` declares `USE /server-settings/mibs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /server-settings/proxy
`src/api/router.ts` declares `USE /server-settings/proxy` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /subnets
`src/api/router.ts` declares `USE /subnets` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /uploads
`src/app.ts` declares `USE /uploads` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /users
`src/api/router.ts` declares `USE /users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /utilization
`src/api/router.ts` declares `USE /utilization` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: demo.mjs (5107 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/app.js (2168 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/assets.js (13918 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/events.js (1583 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/integrations.js (6112 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/ip-panel.js (1402 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/map.js (2492 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/mobile/asset-detail.js (1603 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/server-settings.js (7322 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/subnets.js (1281 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/users.js (1750 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/api/routes/assets.ts (3561 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/api/routes/integrations.ts (7839 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/api/routes/map.ts (1189 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/api/routes/serverSettings.ts (1923 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/agentInstallService.ts (1647 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/capacityAdvisorService.ts (1219 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/capacityService.ts (1724 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/fortimanagerService.ts (2739 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/monitoringService.ts (8775 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/services/reservationService.ts (1353 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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.