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

softwaresoftware-dev/mindframe

https://github.com/softwaresoftware-dev/mindframe · scanned 2026-06-16 00:17 UTC (2 months, 2 weeks ago)

51 raw signals (0 security + 51 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 51 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
63.7
/100
Security checks
64
0 findings
System graph
64
100.0% cov · 51 findings
Critical
0
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 0 High 13 Medium 10 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 51 Crowd 0 Layer: Frontend 1 Security 19 Quality 9 Api 22
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 63.7/100 with 100.0% coverage. It contains 300 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 51 findings — concentrated in api (22), security (19), quality (9). Risk profile is high: 0 critical, 13 high, 10 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 48 of 51 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/watches/${encodeURIComponent(id)}/${act} (dashboard/public/main.js:156)
`dashboard/public/main.js:156` calls `POST /api/watches/${encodeURIComponent(id)}/${act}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/watches/<p>/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_frame` without auth dependency — dashboard/server/server.py:877
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:877 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_dashboard_event` without auth dependency — dashboard/server/server.py:1255
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:1255 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `archive_frame` without auth dependency — dashboard/server/server.py:330
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:330 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_mindframe` without auth dependency — dashboard/server/server.py:623
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:623 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `frame_message` without auth dependency — dashboard/server/server.py:832
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:832 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `open_watch` without auth dependency — dashboard/server/server.py:2159
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:2159 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pause_watch` without auth dependency — dashboard/server/server.py:2148
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:2148 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resume_watch` without auth dependency — dashboard/server/server.py:2154
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:2154 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_frame_kind` without auth dependency — dashboard/server/server.py:848
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:848 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stop_run` without auth dependency — dashboard/server/server.py:2254
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:2254 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `unarchive_frame` without auth dependency — dashboard/server/server.py:336
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:336 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `frame_data_put` without auth dependency — dashboard/server/server.py:964
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
dashboard/server/server.py:964 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/public/main.js:618
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 authority lacks a verifier contract: skills/open/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
skills/open/SKILL.md VerificationSkill file
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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/public/main.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/public/main.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/public/proto-home-1.html:106
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/public/proto-home-1.html:106 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/public/proto-home-2.html:89
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/public/proto-home-2.html:89 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/public/proto-home-3.html:75
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/public/proto-home-3.html:75 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard/public/surface.html:277
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard/public/surface.html:277 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in dashboard/public/surface.html:538
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
dashboard/public/surface.html:538 Domparser html parse
low System graph security security conf 1.00 Insecure pattern 'document_write' in dashboard/public/main.js:809
Found a known-risky pattern (document_write). Review and replace if possible.
dashboard/public/main.js:809 Document write
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 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 api Wiring conf 1.00 Unused endpoint: DELETE /api/frame/{mid}
`dashboard/server/server.py` declares `DELETE /api/frame/{mid}` 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 /api/agents
`dashboard/server/server.py` declares `GET /api/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: GET /api/events
`dashboard/server/server.py` declares `GET /api/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: GET /api/frame/{mid}/activity
`dashboard/server/server.py` declares `GET /api/frame/{mid}/activity` 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 /api/frame/{mid}/data
`dashboard/server/server.py` declares `GET /api/frame/{mid}/data` 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 /api/frame/{mid}/data/{key}
`dashboard/server/server.py` declares `GET /api/frame/{mid}/data/{key}` 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 /api/frame/{mid}/export
`dashboard/server/server.py` declares `GET /api/frame/{mid}/export` 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 /api/frame/{mid}/page
`dashboard/server/server.py` declares `GET /api/frame/{mid}/page` 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 /api/frame/{mid}/rev
`dashboard/server/server.py` declares `GET /api/frame/{mid}/rev` 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 /api/frames/activity
`dashboard/server/server.py` declares `GET /api/frames/activity` 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 /api/vault/entries
`dashboard/server/server.py` declares `GET /api/vault/entries` 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 /artifacts/{sid}/{path:path}
`dashboard/server/server.py` declares `GET /artifacts/{sid}/{path:path}` 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 /m/{mid}
`dashboard/server/server.py` declares `GET /m/{mid}` 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 /{full_path:path}
`dashboard/server/server.py` declares `GET /{full_path:path}` 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 /api/dashboard-event
`dashboard/server/server.py` declares `POST /api/dashboard-event` 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 /api/frame/{mid}/kind
`dashboard/server/server.py` declares `POST /api/frame/{mid}/kind` 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 /api/frame/{mid}/message
`dashboard/server/server.py` declares `POST /api/frame/{mid}/message` 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 /api/frame/{mid}/unarchive
`dashboard/server/server.py` declares `POST /api/frame/{mid}/unarchive` 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 /api/watches/{rid}/pause
`dashboard/server/server.py` declares `POST /api/watches/{rid}/pause` 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 /api/watches/{rid}/resume
`dashboard/server/server.py` declares `POST /api/watches/{rid}/resume` 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: PUT /api/frame/{mid}/data/{key}
`dashboard/server/server.py` declares `PUT /api/frame/{mid}/data/{key}` 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: dashboard/server/server.py (2386 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/0aca6d3b-8a6f-413a-815b-106802ce98bd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0aca6d3b-8a6f-413a-815b-106802ce98bd/

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.