rcourtman
2fae429a7b
## Why Since 3 October, npm advisory GHSA-vfj7-8cjw-p6xm (`braces` <= 3.0.3, no patched release) gives seven high findings in `frontend-modern`. The required frontend dependency audit fails closed on any pull request that changes `package.json` or `package-lock.json`. Every finding was dev-only (`npm audit --omit=dev` was already clean), through two chains: - `tailwindcss` 3 -> `chokidar` 3, `fast-glob`, `micromatch` -> `braces` - `jscpd` 4 -> `@jscpd/finder` -> `fast-glob` -> `micromatch` -> `braces` Every `fast-glob` and `micromatch` release depends on `braces`, so `overrides` cannot fix this. Suppressions, allowlists and severity thresholds are not used. ## What changes - `tailwindcss` 4.3.3 through `@tailwindcss/vite`. `tailwind.config.js`, `postcss.config.js`, `autoprefixer` and the direct `postcss` dependency are removed (Vite still bundles its own PostCSS). - `jscpd` 5.4.0, which has no runtime dependencies. This supersedes Dependabot #2278 (jscpd 5.3.2). - `npm audit --json` over the full graph: **0 findings**. `braces`, `micromatch`, `fast-glob` and `chokidar` are gone from the lockfile. - `dependencySecurity.test.ts` now rejects any locked `braces` copy. It fails on main's lockfile and passes here. The `autoprefixer` floor is dropped because the package is gone. - Templates were migrated with `@tailwindcss/upgrade`. I reverted 39 false positives where it rewrote prop values and prose (`shape: 'rounded'`, `appearance: 'outline'`, test names containing "blur" or "rounded"). I finished the template-literal classes it skipped. - `src/index.css` was migrated by hand, because the tool turned every `@layer` rule into an `@utility`. `src/tailwind-palette.css` is new. - `shared-template-registry.json` retired patterns use the new class names, so the drift audit still matches the source. - `check-assistant-identity.mjs` and `managed-local-backend.mjs` no longer read the deleted config files. ## How v3 rendering is kept Most of v4's defaults differ from v3's. Each item below was found by measuring, not by reading the upgrade guide: | v4 change | Kept as v3 by | |---|---| | OKLCH palette | v3 hex palette pinned, inlined so `/NN` modifiers compile to static colours (no runtime `color-mix`) | | `--font-sans` without `system-ui` (4.3) | v3 font stacks pinned | | Unitless line heights (`text-[11px]` inside `text-xs` went 16px -> 14.67px) | v3 absolute line heights pinned | | Native cascade layers: any utility beats any component rule | former `@layer components` and unlayered rules placed in the utilities layer before and after the generated utilities, matching v3's flat cascade (for example the container-query `hidden sm:table-cell` overrides) | | `space-*`/`divide-*` moved to `:where(> :not(:last-child))` | v3 selectors restored via `@utility`, v4 rules neutralised | | hover only on hover-capable pointers | `@custom-variant hover (&:hover)` | | `dark:` specificity | `@custom-variant dark (&:is(.dark *))` (same as v3) | | border default `currentColor`, ring 1px `currentColor`, placeholder, button cursor, table cells' 1px padding | compat rules in the base layer | | Opacity modifier multiplies a translucent colour (v3 replaced the alpha) | the 900/950 shades Pulse overrode with 25% alpha are opaque now; the 1,203 callers that relied on the implicit alpha say `/25` | | `bg-surface/40`-style modifiers on `var()` colours now render (v3 silently emitted nothing) | the 103 never-rendered tokens are removed | | `pb-safe-or-14 xl:pb-0`: v3 variants came after the custom rule | single-class helpers are now `@utility`, so variants win again | | Utility sort changed from lexical to numeric | see below | ### Sort-order flips v3 sorted `min-h-11` before `min-h-6`, so some caller overrides lost to a shared primitive's base class without anyone noticing. v4 sorts numerically. A runtime scan of 82 states and a static scan of every `Button`/`ButtonLink`/`ActionIconButton`/`CopyValueButton`/`TableCell`/`TableHead`/composed-class call site found these: - **Touch targets** (`min-h-11 min-w-11` on phone; guardrail tests assert them): these now render at their authored 44px. The Machines row action uses `-my-2`, so the 44x44 target fits the 32px row and the table is pixel-identical. The Roles edit/delete buttons, the mobile threshold cancel button and Patrol's Copy ID button get the 44px phone target they were written with. - **Cosmetic overrides v3 never applied** (`justify-start` on Reporting, SSO, drawer-attention, Snooze and Patrol buttons; `align-top` in `DetailSectionTable`; `sm:text-[11px]` on storage headers): these are removed, so the UI renders exactly as it does today. Example: the Snooze menu options stay centred. - **Overrides v3 did apply but v4 would not**: these use the important suffix (`min-h-9!`, `justify-between!`, `flex-nowrap!`). ## Verification - Private mock stack with main (v3) and this branch (v4) served side by side from one backend. A Playwright rig compared every element's computed style and a full-page pixel diff. - **64 states** (16 routes x light/dark x 1440 / 390 with touch emulation): 59 pixel-identical. The other five are mock drift (alert counters, timestamps, tab-strip scroll timing) that was identical on rerun, plus 12 antialiased edge pixels on vSphere at 390. - Hover (desktop and touch), keyboard focus and row expansion: identical. Focus keeps the same 2px blue ring. The invisible transparent outline is now `outline-style: none`, and `outline-hidden` keeps it in forced-colours mode. - Docs page: pixel-identical. Prose colours differ by at most 2/255, because `@tailwindcss/typography` reads v4's palette. - `format:check`, `lint` (eslint, theme, copy, canonical-platform, form-label, table-row, external-domain and planning-doc audits), `type-check`: pass. `make frontend` and `check:bundlesize`: pass. CSS is 31.12 kB gzip against a 31.59 kB baseline. - `vitest`: 21,758 passed. The only failures are the six `agentInstallCommand` lifecycle tests, which need GNU `stat` and fail on macOS on main too. - `npm run lint:cpd` with jscpd 5: exit 0, 39 clones (0.50%) against the 3% threshold. jscpd 4 reported 130 clones because it also re-scanned every TSX file as JavaScript despite the config's `format` list. jscpd 5 honours that list. - `scripts/npm-audit-retry.sh all`: no vulnerabilities. ## Browser support (product consequence) Tailwind CSS 4 is supported on **Safari 16.4+, Chrome 111+ and Firefox 128+**; below that it is untested. What this build actually needs is less than that. The production CSS has media range syntax and nesting lowered, and palette opacity modifiers folded to static colours, so its hard requirement is cascade layers: Safari 15.4, Chrome 99, Firefox 97. Pulse's platform tables already need container queries (Safari 16, Chrome 105, Firefox 110) to lay out correctly. So a browser that renders Pulse correctly today should still do so, but anything between those floors and Tailwind's tested floor (Safari 16.0-16.3, Firefox 110-127, including the Firefox 115 ESR that Windows 7/8.1 users are stuck on) is untested. I found no issue reports from users on such browsers. Supersedes #2278 (jscpd 5.3.2).
Pulse
Real-time Proxmox, Docker and Kubernetes monitoring that finds what needs attention.
Pulse is a self-hosted monitoring workspace for Proxmox, Docker, Kubernetes, TrueNAS, physical and virtual machines, and early-access VMware vSphere environments. It combines live infrastructure state, history, alerts, recovery visibility, and scheduled health checks without requiring a conventional enterprise monitoring stack.
Why Pulse
- It watches between visits. Alerts and Pulse Patrol find failed backups, capacity pressure, restart loops, unhealthy containers, clock drift, and other problems that dashboards cannot surface when nobody is looking.
- It keeps each platform familiar. Proxmox, Docker, Kubernetes, TrueNAS, vSphere, and machines have dedicated views, backed by one shared resource model for search, alerts, history, and investigation.
- It stays operator-controlled. Credentials are encrypted at rest, API tokens are scoped, agent commands are disabled by default, and governed fixes require the configured policy and approval path.
Platform coverage
| Platform | Coverage |
|---|---|
| Proxmox VE, PBS, and PMG | Nodes, guests, storage, backups, replication, Ceph, mail gateways, and alerts |
| Docker and Podman | Hosts, containers, Compose projects, Swarm services, health, images, and updates |
| Kubernetes | Clusters, nodes, workloads, pods, services, storage, and events through the unified agent |
| TrueNAS SCALE and CORE | Pools, datasets, disks, snapshots, replication tasks, apps, VMs, and alerts |
| Linux, Windows, and macOS machines | Host health, filesystems, networking, temperatures, RAID, and availability through the unified agent |
| VMware vSphere | Early-access inventory, hosts, clusters, VMs, datastores, networks, snapshots, and recovery context; validate against your own vCenter before production use |
Platform pages keep storage and recovery information beside the infrastructure it belongs to. Alerts, Actions, and Patrol remain cross-platform views.
Patrol: monitoring that does rounds
Pulse Patrol runs scheduled checks across the current state and recent history of your infrastructure. Community installations can use a local model or their own AI provider for watch-only analysis. Pulse Pro adds investigation and policy-bound fixes with approval, verification, and an audit trail.
Pulse also includes an interactive Assistant and an MCP adapter for external clients such as Claude Code and OpenCode. Both sit on top of the same scoped inventory, metrics, alert, storage, and governed-action contracts.
Quick start
Choose an exact version from the latest release and keep that version pinned during installation.
Docker
docker run -d \
--name pulse \
-p 7655:7655 \
-v pulse_data:/data \
-e PULSE_DEPLOYMENT_METHOD=docker_run \
--restart unless-stopped \
rcourtman/pulse:vX.Y.Z
Open http://<your-ip>:7655 and follow the bootstrap-token setup. Docker host
monitoring is provided by the unified agent; the Pulse server container does
not need the Docker socket.
Proxmox LXC, Linux, and Kubernetes
The installer is signed. Verify install.sh against the pinned
pulse-installer key before running it:
export PULSE_VERSION=vX.Y.Z
curl -fsSLO "https://github.com/rcourtman/Pulse/releases/download/${PULSE_VERSION}/install.sh" &&
curl -fsSLO "https://github.com/rcourtman/Pulse/releases/download/${PULSE_VERSION}/install.sh.sshsig" &&
ssh-keygen -Y verify \
-f <(printf '%s\n' 'pulse-installer namespaces="pulse-install" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMZd/DaH+BldzOkq1A8KVTcFk73nAyrE8aJOyf7i00jm pulse-installer') \
-I pulse-installer \
-n pulse-install \
-s install.sh.sshsig < install.sh &&
bash install.sh --version "${PULSE_VERSION}"
Paste the whole block: installation stops if either download or signature verification fails. Do not run the final command separately to bypass a failure.
The GitHub installer installs the Pulse server. Install and upgrade agents (including v5-to-v6 agent upgrades) with the per-host command generated under Settings → Infrastructure → Install on a host.
Do you need an agent?
Often not. Proxmox VE, PBS, and PMG are monitored through the Proxmox API with a read-only token, so nothing runs on the host and the generated setup script creates a privilege-separated monitoring user. Install the unified agent only where you want data the platform API cannot provide, such as host SMART health, temperatures, Docker hosts, or standalone machines.
The agent is operator-controlled by design. Command execution is off by
default, the local listener binds to localhost, and generated systemd units
ship hardened. On Linux, the installer's --least-privilege profile runs the
service as a dedicated non-root user, with optional scoped sudo grants for
the few collectors that need elevation. The
agent security model documents exactly what the
agent can and cannot do at each privilege level.
Important
GitHub release assets and
rcourtman/pulseimages are Community builds. Relay, Pro, and eligible legacy customers should use the private image or Linux archive provided by the Pulse download portal. Replacing a private Pro runtime with a public Community build removes its private runtime hooks.
Editions
- Community — self-hosted monitoring, seven days of metric history, core SSO, update alerts, and Patrol with your own provider or local model.
- Pro — Community plus Patrol investigation, governed fixes, ninety days of history, centralized agent profiles, RBAC, audit logging, and reporting.
- MSP — for managed service providers: one Pulse Account running many client workspaces, each with an isolated Pulse runtime — separate dashboards, alerts, users, audit history, and reports. Free sixty-day two-client evaluation at Pulse for MSPs.
Relay is no longer sold. Existing Relay subscribers receive Pro features at their current price for as long as their subscription continues. Existing paired phones keep working until 31 March 2027. Relay connects the app, not the web UI. Use your own VPN or tunnel for remote web access. For phone alerts, add an ntfy, Gotify or Pushover destination and open Pulse in your phone's browser.
Core self-hosted monitoring is not gated by monitored-system or child-resource volume. See the runtime-aligned capability reference and current plans for details.
Documentation
- Install and deployment
- Production deployment and security
- Upgrade from Pulse v5
- Releases and update channels
- Configuration
- Platform and agent guides
- Pulse Intelligence
- Security and privacy
- Code signing policy
- Troubleshooting
- API reference and architecture
Localized getting started guides: Deutsch · Español
Development
Pulse uses Go 1.26 and a SolidJS/TypeScript frontend. The managed development
runtime starts the frontend at http://127.0.0.1:5173 and proxies API and
WebSocket traffic to the backend on port 7655.
npm ci
npm --prefix frontend-modern ci
npm run dev
Useful checks:
go test ./...
npm --prefix frontend-modern test
npm --prefix frontend-modern run type-check
python3 scripts/check_public_docs.py
See CONTRIBUTING.md before investing in a code change. Pulse uses an issue-first contribution process and does not normally accept unsolicited pull requests.
Community and support
- Ask questions in GitHub Discussions.
- Report reproducible bugs through GitHub Issues.
- Home Assistant users can use the community-maintained Pulse add-ons.
- If Pulse is useful to you, support its development through GitHub Sponsors or Ko-fi.
License
Everything in this repository is licensed under the MIT License. There is no dual licensing and no commercial or source-available code here.
Pulse Pro is a separate commercial product, built from private sources and distributed through pulserelay.pro. Its use is governed by the Terms of Service, which apply to that product only, not to anything in this repository.