Projectmeetup

Built at [Seattle] Build with Akamai Cloud at GitHub Bellevue

Mithra Security

Mithra Security Mithra is a social-engineering risk scanner for GitHub repos. It warns you when an open-source project your app depends on is being taken over, before any malicious code is introduced. Live: http://mithrasec.com · http://172.232.189.84 (venue network only) Repo: https://github.com/petr1264k/mithra-security Team: Petr Kirsanov and Mikhail Kirsanov Named after the Persian god Mithra, who has a thousand ears and ten thousand eyes and cannot be deceived. Why In 2024 a backdoor in xz Utils (CVE-2024-3094) nearly reached millions of Linux servers. It was the last step of a two-year con: in 2022, new accounts on the public xz-devel mailing list pressed the tired, unpaid maintainer to hand over control. Security scanners read code. This attack showed up first in conversation, and Mithra reads the conversation. User and benefit Developers and security teams who ship apps built on open-source libraries. Paste a GitHub repo and every dependency gets a 0–100 takeover-risk score, with the exact public quotes and links behind it. Watched repos are re-scanned every night. Akamai Cloud services - Linode (Nanode, Seattle): runs the FastAPI app, plus a nightly systemd timer that re-scans watched repos and records risk history. - Managed PostgreSQL 18 + pgvector: scans, risk history, signals, a shared model-result cache, and the 2022 xz pressure emails as embeddings for similarity search. - Object Storage: the evidence. Each project's fetched activity, every scan report and the xz replay dataset, opened from the dashboard through one-hour signed links. - Cloud Firewall: only ports 22 and 80, only from the venue network. - DNS Manager: serves mithrasec.com. - Cloud Inference: three models, below. Inference - qwen3-8-27b tags signals (maintainer burnout, pressure campaign, control handover) as JSON matched to a schema. - gemma-4-26b-a4b-it reads the xz-devel mailing list month by month. Its 262k-token context fits whole threads. - qwen3-embedding-8b + pgvector finds messages close to the 2022 xz pressure emails. Technical choices - Code computes the score, not the model, with fixed weights. The model only finds and quotes signals. Code adjusts each one with GitHub facts: burnout counts only when a maintainer says it, pressure from a brand-new account counts 1.5×, from a known contributor 0.5×. - Caching: model results are cached by content hash in PostgreSQL, shared by the laptop and the server, to protect the shared AI key and GitHub's rate limit. - Least privilege: the server never holds the account token, the storage key reaches one bucket, and the database accepts only the Linode (IPv4 + IPv6) and our laptop. Our idea Existing tools read code or count activity, so they alert after a bad release. Mithra reads the conversation and catches the pressure campaign before the handover: for xz, about two years before the backdoor. It flags situations and shows the evidence behind every flag. Demo 1. mpld3/mpld3, live this month: high (85). Two weeks after its maintainer asked publicly for help, a brand-new account offered to take over triaging issues and reviewing pull requests. The maintainer then warned 10 other repos where the same account had made offers. 2. binbin2000/icloudpd-manager: 14 of 16 dependencies score low. icloudpd scores high (60): its maintainers posted "Looking for new MAINTAINER for the project". 3. xz replay tab, press Play: the risk turns red in May 2022.

// latest_project_recording.mp4
// Project brief

Mithra Security Mithra is a social-engineering risk scanner for GitHub repos. It warns you when an open-source project your app depends on is being taken over, before any malicious code is introduced. Live: http://mithrasec.com · http://172.232.189.84 (venue network only) Repo: https://github.com/petr1264k/mithra-security Team: Petr Kirsanov and Mikhail Kirsanov Named after the Persian god Mithra, who has a thousand ears and ten thousand eyes and cannot be deceived. Why In 2024 a backdoor in xz Utils (CVE-2024-3094) nearly reached millions of Linux servers. It was the last step of a two-year con: in 2022, new accounts on the public xz-devel mailing list pressed the tired, unpaid maintainer to hand over control. Security scanners read code. This attack showed up first in conversation, and Mithra reads the conversation. User and benefit Developers and security teams who ship apps built on open-source libraries. Paste a GitHub repo and every dependency gets a 0–100 takeover-risk score, with the exact public quotes and links behind it. Watched repos are re-scanned every night. Akamai Cloud services - Linode (Nanode, Seattle): runs the FastAPI app, plus a nightly systemd timer that re-scans watched repos and records risk history. - Managed PostgreSQL 18 + pgvector: scans, risk history, signals, a shared model-result cache, and the 2022 xz pressure emails as embeddings for similarity search. - Object Storage: the evidence. Each project's fetched activity, every scan report and the xz replay dataset, opened from the dashboard through one-hour signed links. - Cloud Firewall: only ports 22 and 80, only from the venue network. - DNS Manager: serves mithrasec.com. - Cloud Inference: three models, below. Inference - qwen3-8-27b tags signals (maintainer burnout, pressure campaign, control handover) as JSON matched to a schema. - gemma-4-26b-a4b-it reads the xz-devel mailing list month by month. Its 262k-token context fits whole threads. - qwen3-embedding-8b + pgvector finds messages close to the 2022 xz pressure emails. Technical choices - Code computes the score, not the model, with fixed weights. The model only finds and quotes signals. Code adjusts each one with GitHub facts: burnout counts only when a maintainer says it, pressure from a brand-new account counts 1.5×, from a known contributor 0.5×. - Caching: model results are cached by content hash in PostgreSQL, shared by the laptop and the server, to protect the shared AI key and GitHub's rate limit. - Least privilege: the server never holds the account token, the storage key reaches one bucket, and the database accepts only the Linode (IPv4 + IPv6) and our laptop. Our idea Existing tools read code or count activity, so they alert after a bad release. Mithra reads the conversation and catches the pressure campaign before the handover: for xz, about two years before the backdoor. It flags situations and shows the evidence behind every flag. Demo 1. mpld3/mpld3, live this month: high (85). Two weeks after its maintainer asked publicly for help, a brand-new account offered to take over triaging issues and reviewing pull requests. The maintainer then warned 10 other repos where the same account had made offers. 2. binbin2000/icloudpd-manager: 14 of 16 dependencies score low. icloudpd scores high (60): its maintainers posted "Looking for new MAINTAINER for the project". 3. xz replay tab, press Play: the risk turns red in May 2022.

// Built with
AkamaiPython 3.11, FastAPI, Uvicorn, PostgreSQL 18 + pgvector, psycopg, boto3 (S3 API for Object Storage), OpenAI Python SDK (for Akamai Cloud Inference), httpx, GitHub REST API, PyPI and npm registry APIs, plain HTML/JavaScript, systemd, uv
// Watch & explore
// More from this event

Keep exploring what builders shipped.

All projects →

Bainbridge

hedgefinder

kalshi hedge

Sahil Bhatt's team

Retry Storm

# CascadeIQ Virtual resilience audit: **AI interprets** an incident → **deterministic simulation** → **AI mitigation** → **verified rerun**. Hackathon prototype (Akamai Seattle AI Hackathon, Nov 2026). **Repo:** https://github.com/Sahil9477/CascadeIQ **Demo:** http://127.0.0.1:8000/ (`uv run serve.py`) **Active branch:** `main` ## Judging ```text User and task: CS / cloud students (and judges) learning why retry storms break checkout paths; they run Lab 01, see the outage, pick a mitigation, and verify it. Benefit: Turns an abstract SRE failure into a hands-on lab: AI proposes, deterministic sim proves, shareable /runs/{uuid} for grading. Services: Akamai Inference (Qwen interpret + recommend; Gemma chart review); Managed Postgres (persist audit runs / share links); Linode Types API (published compute pricing beside outage loss). App can run on a Linode VM (deploy/) — laptop demo uses serve.py. Inference: qwen3-8-27b for scenario JSON + allowlisted mitigation; gemma-4-26b-a4b-it reads the before chart as a hint (metrics win). Checked by same-seed Python verify and fixture vs live flags (inference_used). Technical choice: Simulator owns truth — models never invent metrics; allowlist + re-sim with same seed so AI can’t fake a win. Our idea: Scenario-first teaching lab (Build → Cost → Break → Fix → Learn), two-model diagnose with Python as the judge. Demo: Start Lab → untick fixtures → Run audit → Ask Qwen → Verify → Save → open /runs/{uuid}. Known limits: No public Linode app URL until Nanode is provisioned; shared minute token budget (429); retry_cap_reduction may show clearer wins than backoff alone. ``` ## Team | Owner | Owns | |---|---| | **Sahil** | Deterministic simulator, Qwen interpret/recommend, FastAPI `/api/interpret\|audit\|recommend\|verify`, contracts/fixtures, Lab 01 + catalog/cost panel | | **Danny** | Interactive dashboard (`static/` instrument), Postgres `/api/runs`, `serve.py`, Linode `deploy/` | ## Quick start ```bash cd ~/Desktop/CascadeIQ git checkout main cp .env.example .env # paste AKAMAI_API_KEY + PG* from workshop / Cloud Manager (never commit .env) uv sync --extra dev uv run serve.py # Lab UI: http://127.0.0.1:8000/ # OpenAPI: http://127.0.0.1:8000/docs # Health: http://127.0.0.1:8000/api/health # Engine-only (no Postgres overlay): # uv run uvicorn cascadeiq.api.main:app --reload --port 8010 uv run pytest -q uv run python scripts/demo_flow.py # live Qwen + sim uv run python scripts/demo_flow.py --fixture uv run python scripts/smoke_runs_db.py # POST/GET /api/runs when PG* set ``` ### Lab 01: The Retry Storm Open `/` after `serve.py` starts. **Start Lab** loads the Gateway→Orders→Payments demo. Leave **Use fixtures** unticked for live Qwen/Gemma; tick it for offline rehearsal (`inference_used` is always shown honestly). Flow: Start Lab → **Run resilience audit** → **Ask Qwen for a mitigation** (Gemma chart review → informed recommend) → **Verify** → **Save** → open `/runs/{uuid}`. Play streams the audit timeline only after a baseline exists. Cost panel uses published Linode types (`GET /api/catalog/compute?region=us-sea`) beside simulated outage loss — never invents prices. ## API See [`docs/cascadeiq-api-contracts.md`](docs/cascadeiq-api-contracts.md) and [`contracts/`](contracts/). - `POST /api/interpret` — Qwen → scenario JSON - `POST /api/audit` — baseline sim time series + metrics - `GET /api/catalog/compute?region=us-sea` — published Linode types (`source: live|unavailable`) - `POST /api/chart/review` — Gemma reads the chart (advisory) - `POST /api/recommend` / `POST /api/recommend/informed` — allowlisted mitigation (optional visual note) - `POST /api/verify` — same seed + mitigation deltas - `POST /api/runs` · `GET /api/runs/{uuid}` — Postgres persist + share (via `serve.py`) Mitigations allowlist only: `bounded_exponential_backoff_seeded_jitter` | `retry_cap_reduction`. ## Layout ``` cascadeiq/engine/ # simulator + schemas cascadeiq/inference/ # Akamai Qwen client cascadeiq/api/ # FastAPI intelligence endpoints checks/ # Gemma chart review + informed recommend (Danny) cloud/ # Postgres /api/runs (Danny) serve.py # production entry: app + runs + static static/ # Lab UI + instrument deploy/ # Linode service + deploy.sh contracts/ fixtures/ ``` Do not commit `.env` or API keys. See [`deploy/PROVISIONING.md`](deploy/PROVISIONING.md) for Linode + Managed Postgres checklist.

Akamai

Heyo

CloudHand

# CloudHand CloudHand gives an AI agent a computer it can use from a browser. Run jobs on an Akamai cloud computer that keeps working after you close the tab, or use your Mac to open local apps and run tasks with your installed Codex skills. ## Try the demo 1. Open the [public judge workspace](https://cloudhand-judges.66-175-217-106.sslip.io/). No sign-in is required. 2. Ask **Calculate 27 × 14 in Calculator** and choose **Confirm action**. 3. CloudHand opens Calculator on Akamai and reports the result, **378**, in the chat. You can also find the completed run under **Akamai computer → Runs**. [Watch the 35-second walkthrough](CloudHand-Demo.mp4) ## Use your Mac Open the [local Mac workspace](http://127.0.0.1:4317/) while CloudHand is running on your Mac. Try **Open Notes on my Mac** or **Open Downloads in Finder**. Your Mac needs to be awake and have the permissions required for the action. To use an installed Codex skill, sign in to the Codex CLI on your Mac, choose **Model → Codex on this Mac**, then select a skill under **+ → Plugins & skills**. ## Run from source From the CloudHand repository, use Node.js 24, npm, and Python 3.10 or later. ```sh npm ci npm run build npm start ``` Open [http://127.0.0.1:4317/](http://127.0.0.1:4317/). Use `npm test` to run the automated checks.