Security
Tokens on the host. Documentation only on the branch.
SpecDox is a local single-operator tool. GitLab tokens never leave the configuration file through the API. Unpublished pages stay versioned and leave the menu.
Controls
Product behaviour operators can show
Tokens stay on the host
GitLab tokens are per remote host in the configuration file. They are never returned by the API.
Documentation only on the branch
Publishing stages only the three documentation trees. Other files in the checkout are never part of the Merge Request.
Drafts are not published
A page marked unpublished stays in the repository and leaves the generated menu, so a draft never reaches readers while still being versioned.
Local operator, no sign-in gate
SpecDox is a single-operator tool on the machine that holds the checkouts. There is no product account database and no public write API for strangers.
Tokens
What lives where
- GitLab token
- Host then token in the env file. Used only to open and update Merge Requests. Never returned by the API.
- Registered project repositories
- The service user must be able to read every checkout. SpecDox does not copy repositories into a second store.
- Drafts
- Unpublished pages stay on disk and leave the generated menu. A draft is versioned without reaching readers.
- Report a vulnerability
- Use the contact form with a description and reproduction. Do not file public issues with exploit detail.