Skip to content

Security: asdecided/WayfinderRouter

Security

SECURITY.md

Security Policy

Reporting a vulnerability

Please report security issues privately — don't open a public issue or pull request.

Use GitHub's private vulnerability reporting: Report a vulnerability (the repo's Security → Advisories → Report a vulnerability). We'll acknowledge within a few days and keep you posted as we work on a fix.

Supported versions

The standalone wayfinder-router package follows CalVer; Wayfinder Desktop follows SemVer. Each product line ships fixes on its latest release. Please reproduce against the most recent applicable router or Desktop version before reporting.

Scope & design posture

A few properties are load-bearing, and reports that undermine them are especially welcome:

  • The scored decision path is offline, deterministic, and keyless (WF-ADR-0001) — it makes no model call, opens no network connection, and reads no credential to route a prompt.
  • Provider keys are read from the environment at request time and are never written to config, logs, or disk (WF-ADR-0004). Virtual gateway keys are stored only as SHA-256 hashes, never in plaintext.
  • Prompt text is never logged or persisted by the decision or metrics paths.

The default local surface refuses to bind beyond loopback. The explicit managed data plane requires virtual-key authentication and excludes operator/diagnostic routes (WF-ADR-0050). Reports that find a way around either boundary are in scope.

Out of scope: vulnerabilities in the upstream providers you point the gateway at, or failures in a TLS ingress/service mesh outside the Wayfinder process.

There aren't any published security advisories