Client-server secret leak candidates
What a client-server-leak finding of fallow security means, why it matters and how to fix it.
What it reports
Client-bound code reaches a non-public env read.
Security explains how fallow finds it.
Why it matters
client-server-leak reports a candidate when a use client module can transitively reach a static non-public process.env or import.meta.env read. Public-by-convention env prefixes are treated as public. The finding is advisory and still needs bundle, framework, and runtime verification before treating it as a real exposure.
Example
A module marked use client imports code that reads a non-public process.env or import.meta.env value through a static path.
Fix
Keep non-public env reads on the server side, move the value behind an API boundary, or rename only intentionally public values to the framework's public prefix.
Facts
| Fact | Value |
|---|---|
| Issue type | client-server-leak |
| Rule id in SARIF output | security/client-server-leak |
| Command | fallow security |
| Default severity | off |
| Suppression comment | // fallow-ignore-file security-client-server-leak |
Fixable with fallow fix | No |
| Opt-in | Yes |