Files
Rohit Ghumare 91c78e759f chore(deps): bundle Dependabot bumps + clear all 8 audit vulns (#779)
Bundles the two open Dependabot PRs (#497 root, #760 website), drops
the iii-sdk bump per current support window, and pins transitive
overrides so 'npm audit' is clean.

Root (package.json)

- @anthropic-ai/sdk     ^0.93.0   -> ^0.100.1   (minor)
- tsdown                ^0.20.3   -> ^0.21.10   (minor; 0.22.x bumps node engine to >=22.18 which would break our engines.node = >=20)
- @types/node           ^25.7.0   -> ^25.9.1    (dev, patch)
- iii-sdk               0.11.2    unchanged     (engine pin stays per current support; 0.17.x removes triggerVoid + has API drift)

Transitive vuln pins (npm overrides)

- qs           >=6.15.2  (GHSA-q8mj-m7cp-5q26, DoS)
- ws           >=8.21.0  (GHSA-58qx-3vcg-4xpx, uninitialized memory disclosure)
- protobufjs   >=7.5.8   (GHSA-xq3m-2v4x-88gg + 8 others — pulled in transitively via the optional @xenova/transformers/onnxruntime-web/onnx-proto chain; 'npm audit fix --force' would downgrade @xenova/transformers to 2.0.1, the override avoids that)

Website (website/package.json)

- next          ^16.2.6  -> ^16.2.7   (patch)
- react / react-dom  ^19.2.6 -> ^19.2.7   (patch)
- @types/node   ^25.7.0 -> ^25.9.1   (dev)
- @types/react  ^19.2.14 -> ^19.2.16 (dev)

Lockfile hygiene

- Untrack website/package-lock.json (was the only tracked lockfile;
  conflicts with the repo's existing no-lockfile rule in the root
  .gitignore)
- Add package-lock.json / pnpm-lock.yaml / yarn.lock to
  website/.gitignore to match the root convention

Results

- 'npm audit' (root): 8 -> 0 vulnerabilities
- 'npm audit' (website): 0 -> 0 vulnerabilities
- 'npm install': no EBADENGINE warnings on node 20.x
- 'npm run build': clean
- 'npm test': 120 files / 1293 tests passing
- 'cd website && npm run build': static generation completes for all 5 routes
2026-06-02 10:32:59 +01:00
..

agentmemory website

Next.js 15 App Router landing page for agentmemory. Lamborghini-inspired black + gold design system. Deploys to Vercel with zero config.

Stack

  • Next.js 15.1 (App Router, React 19, TypeScript 5.7)
  • next/font for Archivo + JetBrains Mono
  • CSS Modules + one globals.css
  • No Tailwind, no bundler config, no client-side routing

Local dev

cd website
npm install
npm run dev
# open http://localhost:3000

Deploy (Vercel)

Two options:

  1. Import the repo on vercel.com and set Root Directory to website/. That's it.
  2. Or npx vercel from the website/ directory.

No env vars required. Node 20 LTS or newer.

Structure

website/
  app/
    layout.tsx      — <html> + fonts + metadata + viewport
    page.tsx        — composes the landing sections in order
    globals.css     — design tokens, buttons, section-head utilities
  components/
    Nav.tsx         — hexagonal bull mark + menu
    Hero.tsx        — title + lede + CTAs
    MemoryGraph.tsx — client canvas animation + hexagonal pause + scroll rail
    Stats.tsx       — counter-up on intersect
    Primitives.tsx  — three cards with 3D mouse tilt
    LiveTerminal.tsx — typewriter replay of memory.recall + consolidate
    Compare.tsx     — agentmemory vs Mem0/Letta/Cognee table
    Agents.tsx      — supported-agents grid
    Install.tsx     — click-to-copy npm + console commands
    Footer.tsx      — source / changelog / license links
    ScrollProgress.tsx — thin gold progress bar at the top of the viewport
  next.config.ts
  tsconfig.json
  package.json

Each interactive component is a "use client" island. Everything else renders on the server.

Design source

/DESIGN.md at the repo root (generated by npx getdesign@latest add lamborghini). Colors, type, spacing rules live there. Every new component should reference it first.