Linkwright

Security Policy — Linkwright for Jira

Effective date: 6 November 2026

Architecture

Linkwright for Jira runs entirely on Atlassian Forge. Its code executes on Atlassian’s infrastructure and its data lives in the Forge storage of each customer’s Jira site, isolated from every other customer. We operate no server, database or log pipeline of our own.

Authentication of incoming data

The only inbound endpoint is the web trigger that receives GitHub webhooks. Every delivery must carry a valid HMAC-SHA256 signature computed with a secret unique to the customer’s site; the signature is checked in constant time on the raw request body. Unsigned, mis-signed or malformed deliveries are rejected. Replayed deliveries are detected and ignored.

Least privilege

Secrets

The GitHub App private key is held in Forge encrypted environment variables. Installation tokens and per-site webhook secrets are held in Forge encrypted storage. The GitHub OAuth token of the person who associates an organization is held and refreshed by Forge. No secret is written to logs or source code. The one secret in a URL is the code of an owner invitation link, by design: it is shown once, works once, and only its hash is stored.

Data handling

Logs contain identifiers, repository, branch and GitHub account names, issue keys, counters and error messages. The app does not write commit messages, author names, tokens or secrets to them. When Jira refuses data, up to 500 characters of its answer are logged with any email address removed; that answer could quote what it refuses. Database queries are parameterized. See the Privacy Policy for the full list of data processed and retention.

Dependencies

Production dependencies are watched by Dependabot alerts and npm audit. Some findings sit in packages that Atlassian’s Forge libraries pull in; those are assessed for what can be reached at run time, and stay until Atlassian updates its libraries when they cannot be.

Reporting a vulnerability

Email security@linkwright.io. We acknowledge reports within 2 business days and fix vulnerabilities within the timeframes of the Atlassian Marketplace Security Bug Fix Policy (critical: 10 days). Please do not disclose publicly before a fix is released.