Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Linear integration that can read and modify Linear workspace data when the user invokes its documented commands.
Install this only if you are comfortable giving the skill a Linear personal API key with whatever workspace permissions that key has. Use a limited or dedicated Linear token if possible, and be careful with create, update, move, post-comment, and sync-commit commands because they make live changes without a dry-run or confirmation step.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
### 1. Get your Linear API key
1. Open Linear → **Settings → API → Personal API keys**
2. Click **Create key**, give it a name, copy the value (`lin_api_...`)
### 2. Set the environment variable
The skill exposes multiple state-changing operations such as creating and updating issues/projects, moving issues, posting comments, and syncing from commit messages, but the interface provides no confirmation, dry-run mode, or explicit warning before executing them. In an agent setting, this increases the risk of unintended or prompt-induced actions against a live Linear workspace, especially because the skill accepts commands directly from stdin/CLI and dispatches them immediately.
The manifest advertises creation, update, move, comment, project, and commit-sync capabilities against a live Linear workspace, but the description does not clearly warn users that invoking these commands will modify external project-management data. This increases the risk of users triggering state-changing actions without informed consent, especially because several commands can alter issues or projects at scale.
The manifest requests a personal Linear API key but does not disclose that workspace data, issue content, comments, and project metadata will be transmitted to Linear's API when the skill is used. Users may supply sensitive credentials and organizational data without adequate notice about the privacy and data-flow implications.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
const https = require('https');
const LINEAR_ENDPOINT = 'https://api.linear.app/graphql';
class LinearClient {
/**
The function parses commit messages and then sends GraphQL requests that can change Linear issue state, culminating in an issueUpdate mutation. Although the top-level docstring states the function will move issues to a done state, there is no confirmation prompt or explicit user-facing disclosure before performing this potentially workflow-affecting remote update.
The README states that sync-commit will "auto-close referenced issues," which can change issue state based on parsed commit messages. While the capability is documented, there is no explicit warning that this may modify multiple issues automatically or unintentionally if commit text is misparsed.
No suspicious patterns detected.