# GitHub in ninedot

Repos, and what each business is built with. Your repos (name, homepage, last push) and, during setup, a repo's package.json and the names of its root files.

## What you get
- Each repo as a service on the business it builds, matched by its homepage (exact)
- What a business runs on, from its dependencies and config files, to suggest what to connect (measured)

## Limits
- A fine-grained token covers one owner; connect one per organisation.
- Monorepos are read from the root package.json only.
- Nothing is ever changed on GitHub.

## Connecting

Key: Fine-grained token (read-only), read-only. Contents: Read-only (Metadata is included). Choose the repos, or all of them.
Create it at https://github.com/settings/personal-access-tokens/new, then paste it in ninedot → Vault → GitHub → Connect. It is checked, encrypted at rest and only ever read by ninedot's servers.

## Questions
**Does ninedot read my code?** No. It reads repo names and homepages, and during setup the package.json and the list of files at the root, to suggest what to connect. Source files aren't read or stored.

All integrations: https://ninedot.app/integrations · ninedot: https://ninedot.app