1. 1 Introduction
2. 1.1 Terms of Service
3. 1.2 Privacy
4. 1.3 Support
5. 2 Logging in and getting started
6. 2.1 Understanding the difference between the basic and webhook enabled apps
7. 3 Workspaces
8. 3.1 Members administration and access levels
9. 3.2 Hierarchy naming schemes
10. 3.3 Free versus paid licences
11. 3.4 Organizations within a workspace
12. 4 Organizations
13. 4.1 Repos
14. 4.1.1 Mapping an organization to a collection of repos
15. 4.1.2 Setting up ignoring and scanning repos
16. 4.1.3 Supported languages and component discovery
17. 4.1.4 Specific repo page
18. 4.2 Components
19. 4.2.1 Specific component page
20. 5 Roadmap

Setting up ignoring and scanning repos

Not every repo needs to be scanned immediately.

Scannable repos

A repo marked as scannable will enter the scan flow and, once processed, will contribute components and dependency information to the dashboard.

Ignored repos

A repo marked as ignored remains visible but is excluded from normal scanning activity. This is useful for:

• archives,
• experimental repos,
• infrastructure repos that are not relevant to portal reporting,
• or repos you want to onboard later.

New repo defaults

Within an organization, you can define the default state for newly seen repos as one of leave as new, ignore or mark for scanning. That helps teams decide whether new repos should be scanned automatically or require an explicit opt-in.