Skip to content

Security: maxffarrell/tredaro

Security

SECURITY.md

Security policy

Tredaro is pre-1.0 software. Security fixes target the current main branch and the newest release; older releases are not maintained separately.

Reporting a vulnerability

Please report through GitHub private vulnerability reporting. Do not include exploit details, credentials or customer data in public issues. If private reporting is unavailable, open an issue requesting a private reporting channel without disclosing the vulnerability.

Include the affected revision, installation mode, prerequisites, a minimal reproduction and expected behavior. Use disposable test data. A source review or passing CI is not a guarantee of production safety.

Operating an installation

Use Node.js 26.12.1+ on the 26.x line for local and container installations. Vercel-managed installations may use Node.js 24.22.1+ on the 24.x line. These minimums include the CVE-2026-111497 Brotli decoder fix. Rebuild and redeploy existing containers after updating; a source change does not replace a running runtime. For Vercel, verify the provider has applied the patched runtime to the deployment; an inbound WAF rule does not protect outbound Brotli responses.

Use HTTPS, persistent authentication secrets, restricted database access and tested backups. Keep dependencies and releases current. Enable demo mode only on a separate disposable installation. Basic SSO, passkeys and BYOK AI are available in the self-hosted core; operators must configure their identity and model providers.

Public estimate/invoice/booking links expire after 30 days and service-report links after 90 days. Treat them as bearer credentials. See the upgrade notes before upgrading: legacy links are invalidated. Reissue links rather than weakening expiry checks. Keep the existing PostgreSQL role password across deployments; Compose environment changes do not rotate an initialized database's credentials.

Tenant-configured webhooks and integrations accept public HTTP(S) destinations without redirects. For a trusted private integration, an installation operator may set OUTBOUND_PRIVATE_ORIGINS to comma-separated exact origins (scheme, host and port). This grants those tenants access to the allowlisted endpoint; keep the list narrow. Local operator-configured BYOK endpoints retain their own configuration.

Forwarded client IPs are accepted only from exact socket peer IPs configured in TRUSTED_PROXY_IPS. Configure a trusted reverse proxy to replace client-supplied forwarding headers; leave the variable unset for direct access.

There aren't any published security advisories