Skip to content

Security: davis-brown/rallyflare

Security

SECURITY.md

Security policy

Reporting a vulnerability

Please report suspected vulnerabilities privately, not as a public issue.

Use GitHub's private vulnerability reporting (Security → Report a vulnerability). Expect an acknowledgement within a week.

Useful things to include: what an attacker gains, the request or input that triggers it, and whether it reproduces against a local make dev stack or only against the deployed API.

RallyFlare is a personal project with no paid bounty.

Scope

In scope: this repository — the Go API (server/), the Expo app (app/), and the Cloudflare Worker layer (deploy/).

Out of scope: findings in the hosting platforms themselves (Cloudflare, Neon), and reports generated by running a scanner against the deployed site without a demonstrated impact. Please do not run load or denial-of-service tests against the deployed API.

Known unpatched advisories

Two transitive advisories are open and deliberately unfixed, because no applicable fix exists yet. Both are tracked and will clear when the upstream dependency ships.

  • image-size (high) — no patched release exists in any version line. It is reached through react-native → metro, and metro's version is pinned by react-native, so it cannot be upgraded independently of the Expo SDK.
  • decode-uri-component (moderate) — the patched 0.5.0 is ESM-only, but it is reached through the CommonJS query-string@7.1.3 inside expo-router. Forcing it with an override throws ERR_REQUIRE_ESM in expo-router's URL parsing and breaks navigation. npm's suggested remediation is a downgrade of expo-router by 52 major versions, which is not a fix.

Reports that only restate either of these are unlikely to lead to a change. A demonstrated exploit path through RallyFlare's own code is very much wanted.

Handling of secrets

Runtime secrets are Cloudflare Worker secrets, declared by name in deploy/api/wrangler.jsonc and provisioned in CI from GitHub secrets. Local development credentials live in the macOS Keychain via scripts/secret; no credential value belongs in a command, a config file, or a commit.

If you believe a credential has been committed to this repository, report it through the private advisory link above rather than opening an issue.

There aren't any published security advisories