stackblitz-security-basics

Apply StackBlitz security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing StackBlitz security configuration. Trigger with phrases like "stackblitz security", "stackblitz secrets", "secure stackblitz", "stackblitz API key security".

claude-code
3 Tools
stackblitz-pack Plugin
saas packs Category

Allowed Tools

ReadWriteGrep

Provided by Plugin

stackblitz-pack

Claude Code skill pack for StackBlitz (18 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the stackblitz-pack plugin:

/plugin install stackblitz-pack@claude-code-plugins-plus

Click to copy

Instructions

StackBlitz Security Basics

Overview

Security best practices for StackBlitz API keys, tokens, and access control.

Prerequisites

  • StackBlitz SDK installed
  • Understanding of environment variables
  • Access to StackBlitz dashboard

Instructions

Step 1: Configure Environment Variables


# .env (NEVER commit to git)
STACKBLITZ_API_KEY=sk_live_***
STACKBLITZ_SECRET=***

# .gitignore
.env
.env.local
.env.*.local

Step 2: Implement Secret Rotation


# 1. Generate new key in StackBlitz dashboard
# 2. Update environment variable
export STACKBLITZ_API_KEY="new_key_here"

# 3. Verify new key works
curl -H "Authorization: Bearer ${STACKBLITZ_API_KEY}" \
  https://api.stackblitz.com/health

# 4. Revoke old key in dashboard

Step 3: Apply Least Privilege

Environment Recommended Scopes
Development read:*
Staging read:*, write:limited
Production Only required scopes

Output

  • Secure API key storage
  • Environment-specific access controls
  • Audit logging enabled

Error Handling

Security Issue Detection Mitigation
Exposed API key Git scanning Rotate immediately
Excessive scopes Audit logs Reduce permissions
Missing rotation Key age check Schedule rotation

Examples

Service Account Pattern


const clients = {
  reader: new StackBlitzClient({
    apiKey: process.env.STACKBLITZ_READ_KEY,
  }),
  writer: new StackBlitzClient({
    apiKey: process.env.STACKBLITZ_WRITE_KEY,
  }),
};

Webhook Signature Verification


import crypto from 'crypto';

function verifyWebhookSignature(
  payload: string, signature: string, secret: string
): boolean {
  const expected = crypto.createHmac('sha256', secret).update(payload).digest('hex');
  return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}

Security Checklist

  • [ ] API keys in environment variables
  • [ ] .env files in .gitignore
  • [ ] Different keys for dev/staging/prod
  • [ ] Minimal scopes per environment
  • [ ] Webhook signatures validated
  • [ ] Audit logging enabled

Audit Logging


interface AuditEntry {
  timestamp: Date;
  action: string;
  userId: string;
  resource: string;
  result: 'success' | 'failure';
  metadata?: Record<string, any>;
}

async function auditLog(entry: Omit<AuditEntry, 'timestamp'>): Promise<void> {
  const log: AuditEntry = { ...entry, timestamp: new Date() };

  // Log to StackBlitz analytics
  await stackblitzClient.track('audit', log);

  // Also log locally for compliance
  console.log('[AUDIT]', JSON.stringify(log));
}

// Usage
await auditLog({
  action: 'stackblitz.api.call',
  userId: currentUser.id,
  resource: '/v1/resource',
  result: 'success',
});

Resources

Next Steps

For production deployment, see stackblitz-prod-checklist.

Ready to use stackblitz-pack?