This research/prototype repository is not certified or penetration tested. Controls below are limited to inspected source. A clean pattern scan does not prove the absence of all secrets or vulnerabilities.
| Threat / asset | Existing control or required handling | Residual risk |
|---|---|---|
| Scene/bystander data | Local model inference; review all maps, videos and screenshots before sharing. | Uploads/maps are unencrypted local files; voice privacy depends on platform. |
| Unauthenticated LAN control | Host/Origin checks, private IPv4 proxy restriction and blocked redirects. | These are not user authentication; reachable LAN peers can control the server. |
| Untrusted files and resource use | Bounds, validated ids and non-pickle persistence reduce exposure. | Native decoders/dependencies need review; no formal audit or strong user isolation. |
| TLS/private keys | Configured certificate/key support; keep private keys out of Git. | Trusted HTTPS is needed for Safari capture; no automatic provisioning. |
| Assistive misinterpretation | Label estimated depth; never invent a failed range. | No blind-user study, safe navigation result or medical certification. |
Never commit API keys, Wi-Fi credentials, private keys, private addresses or location traces. Use local untracked configuration and placeholders in examples. Rotate previously disclosed credentials; deletion from a working copy does not erase Git history.
The proposed engineering-check workflow uses read-only repository access, no project secrets, no deployment permissions and no physical devices. Review dependency changes. Never disable application-control policy to run a blocked test.
No private vulnerability-reporting channel has been verified for this repository. Do not post working secrets or sensitive exploit details in public issues; use an independently verified private owner contact if available. This file does not claim that branch protection, secret scanning or private reporting has been enabled.
Review frames for faces, serial numbers, locations, network details and open terminals before publication. Preserve actual hardware evidence; never fabricate operation. Power, wiring and physical safety require their own review.