Repository review for security teams

Review the repository boundary#

The Test Chronicle agent runs in a local checkout or CI runner controlled by the customer. It does not install a GitHub App or independently browse repositories.

That boundary is important for approval. The sync process reads repository history from the environment where it is run, extracts test metadata, and sends only the recorded project data needed by the dashboard. The recommended GitHub Actions workflow uses repository checkout plus a scoped Test Chronicle API key, not broad application access.

Ask the key questions#

• What can the sync process read?
• Which metadata leaves the checkout?
• Which GitHub permission and secrets does the workflow receive?
• How are credentials scoped and revoked?
• How are project and account deletion initiated?

The Security and Trust page answers these questions in one place. How repository sync works explains the processing path, and the GitHub Actions guide provides the recommended read-only workflow.

Approval workflow#

Security reviewers can use the public documentation before any repository is connected. Start with the data inventory on Security and Trust, confirm how repository sync processes history, then review the GitHub Actions example for the planned automation path.

If a team starts with local sync, the same boundary applies: the checkout remains customer-controlled and credentials can be rotated from the authenticated product. Pricing and plan choices do not change the core repository access model.