PulseBoard 1.x is the supported line. Fixes land on the latest release.
Please report security issues privately through GitHub's "Report a vulnerability" flow on this repository (Security tab, Advisories), or by contacting the maintainer through the email address on the GitHub profile. Do not open a public issue for a vulnerability.
Please include the affected version, a description of the impact, and steps to reproduce. You should get an acknowledgement within a few days.
- The collect endpoint (
POST /api/collect) is intentionally public: any website visitor's browser must be able to send pageviews. It is rate-limited only by what your deployment puts in front of it, so if event spam is a concern, put PulseBoard behind a reverse proxy with rate limits. - The dashboard and the admin API are protected by a single admin
password (
PULSEBOARD_ADMIN_PASSWORD). Sessions are HMAC-signed cookies scoped to the dashboard only. Use a long random password, and serve PulseBoard over HTTPS in production (for example behind a reverse proxy) so the password and session cookie are not sent in cleartext. - Visitor data minimisation is a design goal: raw IP addresses and raw user agent strings are never written to the database. If you find a code path where they are persisted, treat it as a security issue and report it as above.