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

Repos

Repos are the main source of discovered information by the Silverfish IDP.

Each repository can move through different scan states, for example:

• new,
• waiting for a scan,
• ignored,
• or up to date.

What Silverfish gets from repos

From a repo, the Silverfish IDP can discover:

• supported languages,
• components,
• dependency relationships,
• and source structure information used elsewhere in the portal.

In addition, in a future release, it will also discover quality and compliance metrics for those repos.

Why repo state matters

Not every repository should always be scanned. Some are intentionally excluded, some are still being onboarded, and some may need to be rescanned after changes to code or rules.