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

Components

Components are the software units that the Silverfish IDP discovers inside repos. They are one of the most important concepts in the Dashboard because they connect:

• repos,
• hierarchy structure,
• package identity,
• and dependency analysis.

Why components matter

Repos are often too large to reason about as a single unit. Components allow Silverfish to describe what is actually built and how those built units relate to one another.

Examples of component types

Depending on the source material, a component might represent:

• a package,
• a library,
• an executable,
• or another buildable or publishable unit.

Once components are discovered, the Dashboard will in time be able to ppresent dependency graphs and more precise hierarchical structure of the source code estate for your repos.