Security audit
Security checks for vulnerabilities and agentic risk
This skill behaves like a disclosed ShipStation order-monitoring helper, but users should understand it uses ShipStation credentials and stores local tracking state.
Install only if you are comfortable giving the skill ShipStation API credentials and allowing it to create local state files with order IDs and check timestamps. Keep the .env file out of version control, review any heartbeat or cron setup before enabling recurring checks, and remember that notifications require an external wrapper such as the documented agent heartbeat.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example to .env and add your credentials
cp .env.example .env
# 2. Edit .env with your ShipStation API key + secret
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example to .env and add your credentials
cp .env.example .env
# 2. Edit .env with your ShipStation API key + secret
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Quick Start
```bash
# 1. Copy .env.example to .env and add your credentials
cp .env.example .env
# 2. Edit .env with your ShipStation API key + secret
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example to .env and add your credentials
cp .env.example .env
# 2. Edit .env with your ShipStation API key + secret
The documented purpose says the skill monitors orders and sends alerts, but the behavior described includes local state persistence and output-only JSON/exit codes rather than actual alert delivery. This mismatch can mislead reviewers and users about what data is stored locally and what actions the skill really performs, reducing informed consent and making operational misuse or unsafe deployment more likely.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
const WORKDIR = __dirname;
const STATE_PATH = path.join(WORKDIR, 'shipping-state.json');
const ENV_PATH = path.join(WORKDIR, '.env');
function loadEnv(file) {
const env = {};
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
const WORKDIR = __dirname;
const STATE_PATH = path.join(WORKDIR, 'shipping-state.json');
const ENV_PATH = path.join(WORKDIR, '.env');
function loadEnv(file) {
const env = {};
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
const WORKDIR = __dirname;
const STATE_PATH = path.join(WORKDIR, 'shipping-state.json');
const ENV_PATH = path.join(WORKDIR, '.env');
function loadEnv(file) {
const env = {};
The skill declares required binaries and environment secrets but does not declare an explicit tool/permission scope for network and environment access. That weakens reviewability and least-privilege enforcement, making it easier for an agent runtime to grant broader capabilities than users expect when handling ShipStation API credentials.
This is a markdown file, so vague-trigger review applies. The description says to 'Monitor ShipStation orders, detect issues, and send alerts' and 'Monitor ShipStation for new orders and issues' but does not specify concrete trigger phrases, activation boundaries, or exclusion conditions, which could cause unintended invocation in general order-monitoring contexts.
For markdown files, warnings should be present when behavior may affect user data or system integrity. The document explains that the script maintains state.json and auto-prunes stored order data, but it presents this as implementation detail rather than a user-facing warning that local files will be created and updated in the workspace.
Detected: suspicious.exposed_secret_literal