CrisisSync

Structure

Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.

Languages

Share of indexed source by file size. Binary and vendored files are excluded.

Dependencies

Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.

Feature verification

• Geolocation sync to backendVerified

  App reads device geolocation and syncs it to a remote backend

  Claimed on readmehigh confidence

  • page/common/home/sync-geolocation/index.page.js:8 — Instantiates @zos/sensor Geolocation, starts it, subscribes via onChange, and POSTs lat/long to `${url}/pos`
• Heart rate sync to backendVerified

  App reads heart rate sensor data and syncs it to a remote backend

  Claimed on readmehigh confidence

  • page/common/home/sync-hr/index.page.js:8 — Instantiates @zos/sensor HeartRate, subscribes via onCurrentChange, and POSTs the reading to `${url}/hr` via httpRequest
• JavaScript implementationVerified

  Built with javascript

  Claimed on Devposthigh confidence

  • app.js — Entire app (pages, layouts, app-side service) is written in plain JavaScript
• Threat/proximity detection with alert ("Threats Eliminated")Verified

  The watch detects proximity to a tracked threat ("gunman") location and alerts/vibrates the user when in danger

  Claimed on Devposthigh confidence

  • page/common/home/index/index.page.js:60 — getDistance() computes distance between user's lat/long and a fetched 'gunman' location; on the computed condition it updates UI text to 'You are in danger!' and calls vibrator.start()
  • page/common/home/index/index.page.js:130 — fetchGunmanData() fetches remote threat coordinates via httpRequest GET to `${url}/data`
• ZeppOS smartwatch app (zeppos, zeppapi)Verified

  Built as a Zepp OS watch application using ZeppOS APIs

  Claimed on Devposthigh confidence

  • app.json:1 — Valid ZeppOS v3 app config declaring pages, permissions (heart rate, geolocation), and app-side module
  • app.js:1 — Uses @zeppos/zml BaseApp/App entry point, the standard ZeppOS app bootstrap
• AWS-hosted backend integrationCode-supported

  Built with amazon-web-services as backend infrastructure

  Claimed on Devpostmedium confidence

  • page/common/home/const.js:1 — The sync endpoint URL is `https://us-east-1.aws.data.mongodb-api.com/...`, an AWS-hosted MongoDB Atlas App Services endpoint, but no AWS-specific server code is present in this repo (backend is external/inaccessible)
• Communication/coordination ("Communication Elevated")Code-supported

  The app elevates or improves communication (e.g. between users, or with a central system) during a crisis

  Claimed on Devpostlow confidence

  • page/common/home/index/index.page.js:146 — syncData() posts the user's own location to `${url}/locationData`, which is the only outbound 'communication' path found; no messaging, chat, or multi-user notification code exists
• MongoDB data storageCode-supported

  Built with mongodb for storing synced data

  Claimed on Devpostmedium confidence

  • page/common/home/const.js:1 — URL points to a mongodb-api.com Atlas App Services endpoint used for POST/GET/DELETE of hr, pos, and locationData; actual MongoDB collections/schema are not in this client-only repo

An AI agent derived these features from the project’s Devpost page and readme, then searched the code for each one. Verified features are backed by cited code; claimed-only features had no supporting code, which is not by itself proof a feature is missing.