Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
# Block install scripts by default to reduce supply-chain attack surface.
#
# IMPORTANT: this file only covers installs whose *local prefix* is the repo
# root. npm reads the project config from the local prefix and never walks up
# the directory tree, so `cd client && npm install` and `npm ci --prefix server`
# do NOT see this file — each workspace carries its own .npmrc for that reason
# (client/.npmrc, server/.npmrc, autofixer/.npmrc, browser/.npmrc). Deleting any
# silently reopens an install-time code-execution slot for every dependency in
# that workspace.
#
# Packages with legitimate install scripts are rebuilt explicitly from the
# allowlist in scripts/trusted-rebuilds.js (shared by `npm run setup`,
# scripts/ensure-deps.js, setup.ps1, update.sh/update.ps1 and CI). Currently only the
# server needs any: node-pty (native PTY addon), sharp (insurance — ships
# prebuilt bindings today), and onnxruntime-node / protobufjs (best-effort).
ignore-scripts=true
# Deliberately NOT engine-strict (issue #3863). The Node floor lives in
# scripts/checkNodeVersion.js (MIN_NODE) and is mirrored into this workspace's
# `engines` field, but `engine-strict=true` makes npm treat EBADENGINE as fatal
# for *dependencies* too, not just for this project — so one transitive package
# shipping a narrow range breaks `npm install` on a Node the project fully
# supports. That is not hypothetical: jsdom@30 requires
# `^22.22.2 || ^24.15.0 || >=26`, which a supported Node 24.14 fails. PortOS is
# distributed software installed on many machines and Node patch levels, so the
# floor is enforced by `node scripts/checkNodeVersion.js` at the head of the
# root `setup` / `start` / `dev` scripts instead — a check that gates on this
# project's floor and nothing else. `engines` stays for the npm warning and as
# the machine-readable declaration.
# Skip the advisory lookup `npm install` runs AFTER it has already resolved and
# written node_modules. It only prints a summary, but npm BLOCKS on it — a
# stalled request costs `fetch-timeout` (300s) times `fetch-retries` (2) before
# npm moves on. On 2026-09-03 that endpoint began completing the TLS handshake
# and never answering, and a 0.15s warm install took 153s; every managed install
# path runs four of them in sequence. Set here rather than as `--no-audit` on a
# dozen call sites for the same reason `ignore-scripts` is: npm reads config from
# the local prefix only, so a flag one path forgets is a silent regression.
# Rationale and what enforces dependency safety instead: docs/DEPS.md
# "Inline Audit Policy".
audit=false