Excluding files
Excluding a file or folder stops FossID scanning it at all. Use it for content that isn't part of your product and would only produce noise: test fixtures, generated files, sample data, third-party code you ship under a separate process.
Exclusions don't expire and don't record a reason. To accept a specific finding for a limited time, ignore it instead.
Excluding from the Explorer
- In the Explorer, right-click one or more files or folders.
- Choose FossID: Exclude from Scanning.
FossID adds a rule for each item and confirms: excluded <path> from scanning (.fossidignore). Findings for the excluded files disappear immediately.
To scan an item again, right-click it and choose FossID: Stop Excluding. FossID removes only that item's own rule and confirms: <path> will be scanned again.
- Excluded because of its folder. If the item is excluded only because its whole folder is, FossID asks whether to Stop Excluding Folder, or offers Open Exclusion File so you can edit the rules yourself.
- Excluded by a pattern. If the item is covered by a broader pattern (such as
*.min.js), FossID opens the exclusion file for you to edit.
The exclusion file
Exclusions live in .fossidignore at the root of your workspace folder. It uses the same syntax as .gitignore:
# Generated code
/build/
/src/generated/
# Test fixtures copied from upstream projects
/test/fixtures/
# Minified bundles
*.min.js
# ...but scan this one
!/public/app.min.js
#starts a comment.- A leading
/anchors the rule to the workspace folder root. - A trailing
/matches folders only. *and**are wildcards.!re-includes something an earlier rule excluded.- Matching is case-sensitive.
You can also put rules in .fossid/ignore, which FossID reads after .fossidignore. FossID notices changes to either file immediately.
Commit .fossidignore so your whole team scans the same files.
What exclusion affects
- Automatic scanning skips excluded files entirely.
- Scan Workspace skips excluded files.
- Rescan Current File still scans an excluded file if you ask it to, and tells you so. Use this to check an excluded file without changing the rules.