replit-security-basics
Apply Replit security best practices for secrets and access control.Use when securing API keys, implementing least privilege access,or auditing Replit security configuration.Trigger with phrases like "replit security", "replit secrets","secure replit", "replit API key security".
When & Why to Use This Skill
The Replit Security Basics skill provides a comprehensive framework for securing cloud-based development environments. It guides users through implementing industry-standard security practices such as API key management, secret rotation, and the principle of least privilege, ensuring that Replit projects remain protected against unauthorized access and credential leaks.
Use Cases
- Securing sensitive API keys and tokens by correctly configuring environment variables and .gitignore files to prevent accidental exposure in version control.
- Implementing least privilege access control by defining and applying specific API scopes tailored for development, staging, and production environments.
- Establishing a robust secret rotation workflow to minimize the impact of potential credential compromises and maintain long-term project security.
- Enhancing application monitoring and compliance by integrating audit logging and webhook signature verification into Replit-based services.
| name | replit-security-basics |
|---|---|
| description | | |
| allowed-tools | Read, Write, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Replit Security Basics
Overview
Security best practices for Replit API keys, tokens, and access control.
Prerequisites
- Replit SDK installed
- Understanding of environment variables
- Access to Replit dashboard
Instructions
Step 1: Configure Environment Variables
# .env (NEVER commit to git)
REPLIT_API_KEY=sk_live_***
REPLIT_SECRET=***
# .gitignore
.env
.env.local
.env.*.local
Step 2: Implement Secret Rotation
# 1. Generate new key in Replit dashboard
# 2. Update environment variable
export REPLIT_API_KEY="new_key_here"
# 3. Verify new key works
curl -H "Authorization: Bearer ${REPLIT_API_KEY}" \
https://api.replit.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 ReplitClient({
apiKey: process.env.REPLIT_READ_KEY,
}),
writer: new ReplitClient({
apiKey: process.env.REPLIT_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
-
.envfiles 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 Replit analytics
await replitClient.track('audit', log);
// Also log locally for compliance
console.log('[AUDIT]', JSON.stringify(log));
}
// Usage
await auditLog({
action: 'replit.api.call',
userId: currentUser.id,
resource: '/v1/resource',
result: 'success',
});
Resources
Next Steps
For production deployment, see replit-prod-checklist.