mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
rcourtman
06a68dbff3
Since 3 October the required Frontend check has failed on every open pull request, including Go-only ones, because of GHSA-vfj7-8cjw-p6xm (`braces` <= 3.0.3, high, no patched release). `braces` reaches the frontend graph only through dev-only `tailwindcss` 3 and `jscpd` 4. `npm audit --omit=dev` is clean, so the shipped bundle is not affected. A pull request that leaves `package.json` and `package-lock.json` untouched has the same dependency graph as its base commit. It can neither add a finding nor remove one, so failing it blocks every fix without making anything safer. ## What changes `scripts/npm-audit-retry.sh` now treats findings the same way it already treated an unreachable advisory endpoint: - **The change moves the dependency graph, or edits the runner** (`NPM_AUDIT_REQUIRE_RESULT=true`): any finding at any severity fails, as before. A missing answer also fails. - **The graph is the base commit's** (`NPM_AUDIT_REQUIRE_RESULT=false`): the run warns instead, still naming every finding. A missing answer also only warns, as before. - **Only an explicit `false` relaxes the verdict.** An empty or unrecognised value stays strict. This also tightens the outage path, which previously relaxed on any value other than `true`. The scheduled `npm-audit` scan and the daily dependency advisory watch keep the strict default. An inherited advisory therefore still fails once a day until the graph is fixed; `test_dependency_advisory_watch.py` now proves this. No severity threshold, allowlist or suppression is added. ## Landing This change edits the runner, so its own Frontend audit runs in strict mode and fails on this same advisory. It cannot pass the required checks, so it lands only by an explicit maintainer merge. That is intentional: the policy is relaxed by a human decision, never by a change passing its own check. Removing `braces` for real means migrating to Tailwind 4 and jscpd 5.4.0; that is tracked separately. Dependency PRs (#2352, #2278) stay blocked until that lands. ## Verification - `scripts/tests/test-npm-audit-retry.sh`: 19 cases pass. - `test_npm_audit_retry.py` and `test_dependency_advisory_watch.py` pass. - `TestFrontendDependencySecurityAuditsAreRequired` passes. - `check_workflow_trust.py` passes. - The real runner against main's lockfile exits 0 with the warning and all 7 findings named when `NPM_AUDIT_REQUIRE_RESULT=false`, and exits 1 with `::error::` when it is `true`.
Pulse documentation
Start here for installation, platform setup, security, operations, and Pulse Intelligence. Commands, configuration keys, image names, API fields, and product identifiers remain untranslated in localized guides.
Start here
- Install Pulse — signed Proxmox/Linux installation, Docker, Docker Compose, Kubernetes, and first-run setup.
- Production deployment and security — least-privilege Proxmox setup, root-agent boundaries, discovery, supply-chain verification, plan limits, scale evidence, and a rollout checklist.
- Upgrade from Pulse v5 — migration prerequisites, rollback, agent continuity, and post-upgrade checks.
- Releases and update channels: choosing Stable or Preview, beta and RC expectations, and how releases are tested and promoted.
- Configure Pulse — authentication, notifications, discovery, retention, and system settings.
- Deployment models — data locations, lifecycle, and differences between supported deployment paths.
- Troubleshooting and FAQ — common failures, diagnostics, and operator questions.
Localized getting started guides: Deutsch · Español
Platforms and agents
- Proxmox Backup Server
- Proxmox Mail Gateway
- Docker and Podman
- Kubernetes and Helm
- TrueNAS SCALE and CORE
- Unified Agent
- Agent security
- VM disk monitoring
- ZFS monitoring
- Temperature monitoring
VMware vSphere support is early access. Current builds expose dedicated vSphere inventory and recovery context, but operators should validate the integration against their own vCenter before production use.
Monitoring and operations
- Metrics history
- Recovery data
- Webhooks
- Automatic updates
- Centralized agent management (Pro)
- Operational trust model
- Current product screenshots
Pulse Intelligence
- Assistant, Patrol, and external-agent overview
- Patrol modes and safety
- Assistant safety model
- External agent HTTP and MCP substrate
Patrol watch-only analysis is available on Community with a local model or the operator's own provider. Investigation and governed fixes require the relevant Pulse Pro capabilities.
Security, privacy, and access
- Production deployment and security
- Security review scope
- Authentication and credential storage review packet
- Security guide
- Privacy and telemetry disclosure
- OIDC and SSO
- Proxy authentication
- Role-based access control (Pro)
- Audit logging (Pro)
- Reverse proxy configuration
- Code-signing policy
Plans and managed access
- Community, Relay, and Pro capabilities
- Relay and Pulse Mobile handoff
- Multi-tenant organizations (Enterprise/custom)
- Provider-hosted MSP operations (request-assisted)
Pulse Cloud is not generally available. Ordinary self-hosted Pulse remains the primary installation path; MSP and Enterprise access are explicit commercial paths rather than defaults in self-hosted setup.
Development and reference
Detailed design notes and dated migration specifications may remain in this directory for maintainers, but they are not operator setup guides unless they are linked from the sections above.
Previous versions and migrations
- Upgrade from v4 to v5
- Retired unified-navigation migration — historical context only; current Pulse uses platform-shaped navigation.
- Move a Pulse installation
Found a bug? Use the issue forms. For setup questions, use GitHub Discussions.