Contact support

Tell us what you were trying to do and what happened. We reply by email.

Get started
Ingestion

Choose which files are analyzed

Exclude and include files so ingestion reads the code that matters.

Ingestion skips files that don't affect security, such as images, lock files, and build output. You can tune this per repository. Excluding generated code, vendored libraries, and test fixtures makes ingestion faster and cheaper, and keeps the cards focused on your own code.

Who can do this:Team adminsRepository maintainers

Open the repository and go to Settings › Ingestion. There are two lists. Changes apply from the next ingestion.

Exclude list

Files matching a pattern here are skipped. The list starts with Lighthouse's defaults, plus any patterns in a .relevance-ignore file at the root of your repository.

# generated API clients and test fixtures
src/generated/
tests/fixtures/**
*.min.js

Include list

Files matching a pattern here are always analyzed, even when an exclude pattern also matches. The list starts with any patterns in a .relevance-important file at the root of your repository.

# generated, but defines our auth middleware
src/generated/auth_middleware.py

Pattern rules

  • One pattern per line, in .gitignore style. Lines starting with # are comments.
  • Paths are relative to the repository root.
  • ! negation isn't supported. Use the include list instead.
  • Binary files, generated files, and anything that isn't a regular file (such as symlinks) are always skipped.

Press Validate to check the patterns, then Save.

Still stuck after reading this page?

Contact support

Tell us what you were trying to do and what happened. We reply by email.

On this page