Skip to main content
HighSecretsOWASP A07:2021CWE-798

How to fix: Linear API key in source

Linear personal API keys (lin_api_*) grant full read/write access to a Linear workspace's issues, projects, and comments via the GraphQL API.

Why it matters

An exposed Linear API key lets an attacker read every issue, project, and comment in your workspace (which often contains security reports, credentials shared in comments, and internal roadmap details), create or delete issues, and post comments impersonating the key owner.

Linear personal API keys (lin_api_*) grant full read/write access to a Linear workspace's issues, projects, and comments via the GraphQL API.

How to fix it

  1. 1Revoke the key at linear.app → Settings → API → Personal API keys
  2. 2Prefer a Linear OAuth app / webhook integration with scoped permissions over a personal API key for server integrations
  3. 3Keep the key server-side only; never expose it in client bundles or public repos

Code examples

Server-only Linear client

TypeScript
// Server-only: never import this in a client component
import { LinearClient } from '@linear/sdk';

const linear = new LinearClient({
  apiKey: process.env.LINEAR_API_KEY!, // server-only, lin_api_*
});

export async function getMyIssues() {
  const me = await linear.viewer;
  return me.assignedIssues();
}

References

Detected automatically by VulnRadar. The check id is secret-linear-api-key, stable across every scan so you can filter or diff on it.

See every secrets check

Questions

How severe is Linear API key in source?
VulnRadar rates this high severity in the secrets category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id secret-linear-api-key, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Linear API key in source map to?
It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for linear api key in source

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Linear API key in source | VulnRadar