youdotcom-oss/risk-analysis-server/extend

Extend the risk-analysis server

Where things live

Steps

1. git clone the repo and bun install.
2. Run bun run check && bun test to confirm the baseline is green.
3. Change the file for your target behavior from the table above. Each module

has its own test in src/tests/ that pins its public behavior — change behavior by changing the test first, then the implementation.

1. Verify with bun run check && bun test. All green means your change is

behavior-complete against the pinned contracts.

Deploy your extension

The assets/ folder in this skill holds the container recipe this repo uses:

• assets/Dockerfile — multi-stage oven/bun:1-alpine image, /data volume

for the SQLite database.

• assets/docker-compose.yml — local orchestration with env wiring.

Copy them into your fork and set the env vars the compose file expects (RISK_JWT_SECRET, RISK_ALLOWED_HOSTS, RISK_CRON_SCHEDULE, plus the three API keys: YDC_API_KEY, TYPESAFE_API_KEY, OPENROUTER_API_KEY). Any host that runs a Bun container works.

Gotchas

• The stdio entry (src/stdio.ts) is auth-free by design — do not add auth

there; the HTTP entry is src/server.ts.

• A failed cron handler with an unhandled rejection exits the process; keep

the per-profile try/catch in the cron handler when touching it.

• buildMcpServer runs per request on the HTTP entry — do not capture

mutable state in the factory closure; tenant state flows through userId from the bearer token's sub.