Skip to main content
Review filters decide which of Fossy’s findings actually get posted. You’ll find them under Settings → Code Review → the repository → Review filters, and they can be set at the global, repository, or directory level — see Config Inheritance & Overrides.

​
Minimum severity level

Fossy assigns a severity to every suggestion and only posts the ones at or above the level you pick. The default is Medium.
Too much noise on a big PR is usually a severity problem, not a volume problem. Move to High before reaching for anything else — you keep every real bug and drop the nitpicks. See Reduce code review noise.

​
Apply filters to Fossy Rules

A toggle, off by default.
  • Off — Fossy Rules findings bypass the severity filter. A rule your team wrote is always reported, whatever severity it lands on.
  • On — Fossy Rules go through the same severity filter as every other suggestion.
Leave it off unless your rules are producing more noise than signal. The whole point of a Fossy Rule is that your team already decided it matters.
In fossa-config.yml these two settings live under suggestionControl:
Remember that the file is only read once you enable fossaConfigFileOverridesWebPreferences — see General.

​
Other ways to cut noise

Review filters are a blunt instrument. When you need something more targeted:
  • Ignore paths — skip generated code, lockfiles, and vendored directories entirely. See General.
  • Analysis types — turn off a whole category (e.g. performance) for repositories where it isn’t useful.
  • Directory-level config — apply stricter or looser filters per folder in a monorepo. See Directory Level Config.
  • Fossy Rules — encode what your team actually cares about, so the signal comes from your standards instead of generic advice.