Linear
Read security issue and incident evidence, with a separate credential for optional finding creation.
Configure read access
Create a dedicated Linear personal API key with Read access to the teams in scope. Enter it in Sparta using the API-key authentication scheme. Select OAuth only when supplying an OAuth credential.
Configure the security and vulnerability labels, plus incident and postmortem terms, to match your team's actual issue conventions. Include every relevant production team.
Review collected evidence
Run the connection check and collect evidence. Review issue ownership, status, dates and the configured security workflow.
Change-to-issue linkage also depends on a retained GitHub pull-request sample less than 24 hours old. Collect GitHub evidence first when reviewing that relationship.
Optional finding creation
Creating a Linear issue from a Sparta finding requires a separate LINEAR_WRITE_API_KEY Worker secret with Read and Create issues permissions for the target team. Configure the finding team and labels separately.
Do not put the write key into the read-only evidence connection.