Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(ops): record unreachable bigint-buffer, lodash.set and node-forge advisories and why root @solana/pay stays on 0.2.6
nirholas1ab9ebc15f0d
diff --git a/docs/ops/README.md b/docs/ops/README.mdindex 685c96074..7bda99f30 100644--- a/docs/ops/README.md+++ b/docs/ops/README.md@@ -22,6 +22,7 @@ Start with [gcp-production.md](gcp-production.md); it is the complete operationa| [materialize-fulfillment.md](materialize-fulfillment.md) | Running physical print fulfillment: the operator console, its authorization doors, the adapter contract for wiring a partner, webhook idempotency, and the stall sweep. || [payment-outcomes.md](payment-outcomes.md) | The payment-outcome board (`GET /api/ops/payment-outcomes`): verify-reject, settle-fail, replay, and sponsor-runway signals and how to read them in an incident. || [home-operations.md](home-operations.md) | The Home Assistant lane: why a per-tenant failure never alerts and a correlated one always does, the SLOs (confirmation integrity has none to spend), the three alerts, the correlation query to run before calling anything an incident, and the reliability half: the measured scale envelope, the five-rung backpressure ladder, the seven chaos scenarios and the Cloud Run sizing each number argued for. |+| [security-exceptions.md](security-exceptions.md) | Accepted `npm audit` findings with no upstream patch (bigint-buffer, lodash.set, node-forge): reachability analysis and why the root `@solana/pay` stays on 0.2.6. || [agent-index.md](agent-index.md) | The agent index crawls end to end: the cursor stall both chain legs share, the error-class table, the recovery script, and how the freshness sensor scores each leg. || [solana-rpc-lanes.md](solana-rpc-lanes.md) | The Solana RPC tier end to end: one-sweep diagnosis, per-lane method capability, what must rotate vs fail, config traps, recovery. || [llm-lanes.md](llm-lanes.md) | The LLM provider chain end to end: which rungs serve, why the paid ones are dead, how spend is metered, the one-command Claude rollout, and per-lane probes. |diff --git a/docs/ops/security-exceptions.md b/docs/ops/security-exceptions.mdnew file mode 100644index 000000000..685595e54--- /dev/null+++ b/docs/ops/security-exceptions.md@@ -0,0 +1,31 @@+# Security exceptions (accepted `npm audit` findings)++Durable, citable answers for advisories that `npm audit` at the repo root keeps reporting and that no dependency bump can close. Each entry names the advisory, the chain, why the vulnerable path is unreachable from three.ws code, and the date measured. Re-measure with `npm audit --json` before trusting an entry; delete the entry the day a patched release exists and is installed.++Scope: the ROOT `node_modules` tree only. Vendored worker dependencies are tracked by their own fix orders and must stay byte-identical across workers (`npm run check:vendored`).++## Measured 2026-10-25++| Advisory | Package | Chain | Patched release | Status |+|---|---|---|---|---|+| GHSA-3gc7-fjrx-p6mg (CVSS 7.5, buffer overflow in `toBigIntLE` / `toBufferLE`) | `[email protected]` | `@solana/spl-token` -> `@solana/buffer-layout-utils` -> `bigint-buffer` (also via `@solana/spl-stake-pool` under `@kamino-finance/klend-sdk`) | None. `1.1.5` is the only and latest version. | Accepted, unreachable |+| GHSA-p6mc-m468-83gw (CVSS 7.4, prototype pollution in `lodash.set`) | `[email protected]` | `@bnb-chain/[email protected]` -> `lodash.set` | None. `4.3.2` is the latest; the SDK is at its latest `2.2.2`. | Accepted, unreachable |+| GHSA-86w9-cpqp-85rv (CVSS 7.5, RSA PKCS#1 v1.5 signature verification) | `[email protected]` | `[email protected]` -> `helia` -> `@ipshipyard/libp2p-auto-tls` -> `acme-client` -> `node-forge` | None. `1.4.0` is the registry latest. | Accepted, unreachable |++### bigint-buffer++Reachability: `grep -rn "bigint-buffer\|toBigIntLE\|toBufferLE" api src scripts` finds nothing. The function is only reached inside `@solana/spl-token` / `@solana/buffer-layout-utils` when they decode u64 / u128 fields of SPL account and mint layouts. Those layouts have fixed byte widths set by the library; no three.ws call site passes a caller-chosen length into them. Account data is read from our own RPC lanes, not from user-supplied buffers. Mitigation if this ever changes: validate the buffer length before any direct `bigint-buffer` call and never add one that takes request-derived input.++### lodash.set++Reachability: `@bnb-chain/greenfield-js-sdk` is a live dependency (`api/_lib/bnb/greenfield.js`, `greenfield-write.js`, `vault-store.js` and the vault endpoints), so it is not dead code. `lodash.set` is called inside the SDK on SDK-owned object paths while building its own request structures. three.ws passes bucket names, object names and byte payloads, never an attacker-chosen property path, so no request field becomes a `set` key. Mitigation if this changes: never pass user-controlled strings as path arguments to SDK message builders, and allowlist keys.++### node-forge++Reachability: `grep -rn "agent0-sdk" api src scripts` shows only `api/agents/8004/agent.js` and `api/agents/8004/search.js`, and both import only the constants `DEFAULT_SUBGRAPH_URLS` and `DEFAULT_REGISTRIES`. No `Helia`, libp2p node, or auto-TLS (ACME certificate ordering) is ever constructed, and `grep -rn "helia\|auto-tls" api src scripts` is empty. The vulnerable RSA signature verification therefore never runs. The same dormant chain accounts for the other `helia` / `libp2p` / `@libp2p/kad-dht` / `@libp2p/peer-store` findings in the audit. Mitigation if this changes: do not start a libp2p node inside a request handler.++## `@solana/pay` stays on 0.2.6 at the root++The root pin `^0.2.6` is intentional. `@solana/pay` 1.x (used by `multiplayer/` and `character-studio/` at `1.0.16`, registry latest `1.0.26`) is a rewrite on `@solana/kit`: `findReference` takes a kit `Rpc<GetSignaturesForAddressApi>` and a kit `Address`, and `validateTransfer` takes `Rpc<GetTransactionApi>`, a kit `Signature`, and bigint-based `TransferFields`. The root call sites (`api/_lib/purchase-confirm.js`, `api/_lib/subscription-checkout.js`, `api/marketplace/buy-asset.js`, `api/print/orders/[id]/confirm.js`, `api/_lib/circulation.js`) pass a `@solana/web3.js` `Connection`, `PublicKey` and `BigNumber`, and `findReference(conn, key, { finality })` uses an option name 1.x renamed to `commitment`. A bump swaps in an incompatible API on the payment-verification path. 0.2.6 is the last release of the web3.js API.++Migration, when taken, must move those five verifiers (and their RPC fallback wrapper) to kit together, behind the existing purchase and checkout tests. It is a payments-path rewrite, not a version bump, and is not required to close any advisory above.diff --git a/prompts/finish/_context/production-100-PROGRESS.md b/prompts/finish/_context/production-100-PROGRESS.mdindex 302af47ef..c7d5e2f6b 100644--- a/prompts/finish/_context/production-100-PROGRESS.md+++ b/prompts/finish/_context/production-100-PROGRESS.md@@ -1980,3 +1980,7 @@ Diagnostic test passed unmodified, so branch A: the same-lane resubmit logic is## 2026-10-25 order 453 closed (/healthz world masked as unknown)`checkWorld()` in `api/_lib/ops/subsystem-health.js` now falls back to the durable `ops_alerts` rows (`world-health:status-http` / `status-unreachable`, last_seen within 40 minutes) when the Redis cache entry is missing or stale, so a real outage reports `down` instead of `unknown`. Six new cases in `tests/subsystem-health.test.js`. `STRUCTURE.md` and `deploy/world/README.md` now state that `hyperfy-world` was deleted 2026-10-23. No GCP infra touched. Commit: see git log for the `fix(ops): stop /healthz masking` subject.++## 2026-10-25 order 454 closed (root CVE triage, @solana/pay pin)++Re-measured `npm audit`: bigint-buffer, lodash.set and node-forge have no patched release and are unreachable from three.ws code; accepted with reachability notes in `docs/ops/security-exceptions.md` (linked from `docs/ops/README.md`). The root `@solana/pay` stays on `^0.2.6`: 1.x is a `@solana/kit` rewrite incompatible with the web3.js call sites on the payment path, so no bump was made; kit migration of the five verifiers is the follow-up. No dependency or lockfile change.