deepgram-multi-env-setup
Configures Deepgram multi-environment setups for development, staging, and production, ensuring proper management of API keys and configurations.
Install this skill
Security score
The deepgram-multi-env-setup skill was audited on Feb 25, 2026 and we found 34 security issues across 3 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 130 | throw new Error(`Unknown environment: ${env}`); |
Template literal with variable interpolation in command context
| 134 | throw new Error(`DEEPGRAM_API_KEY not set for ${env}`); |
Template literal with variable interpolation in command context
| 185 | ```yaml |
Template literal with variable interpolation in command context
| 234 | ```yaml |
Template literal with variable interpolation in command context
| 336 | result.errors.push(`API key error: ${projectsError.message}`); |
Template literal with variable interpolation in command context
| 345 | result.errors.push(`Project ${projectId} not accessible`); |
Template literal with variable interpolation in command context
| 392 | console.log(`${env.name.toUpperCase()}`); |
Template literal with variable interpolation in command context
| 393 | console.log(` Valid: ${result.valid ? 'YES' : 'NO'}`); |
Template literal with variable interpolation in command context
| 394 | console.log(` API Key: ${result.apiKeyValid ? 'OK' : 'INVALID'}`); |
Template literal with variable interpolation in command context
| 395 | console.log(` Project Access: ${result.projectAccess ? 'OK' : 'DENIED'}`); |
Template literal with variable interpolation in command context
| 398 | console.log(` Features: ${result.features.join(', ')}`); |
Template literal with variable interpolation in command context
| 403 | result.errors.forEach(e => console.log(` - ${e}`)); |
Template literal with variable interpolation in command context
| 414 | ```hcl |
Access to .env file
| 73 | apiKey: process.env.DEEPGRAM_API_KEY_DEV!, |
Access to .env file
| 74 | projectId: process.env.DEEPGRAM_PROJECT_ID_DEV!, |
Access to .env file
| 90 | apiKey: process.env.DEEPGRAM_API_KEY_STAGING!, |
Access to .env file
| 91 | projectId: process.env.DEEPGRAM_PROJECT_ID_STAGING!, |
Access to .env file
| 107 | apiKey: process.env.DEEPGRAM_API_KEY_PRODUCTION!, |
Access to .env file
| 108 | projectId: process.env.DEEPGRAM_PROJECT_ID_PRODUCTION!, |
Access to .env file
| 126 | const env = process.env.NODE_ENV || 'development'; |
Access to .env file
| 151 | const env = process.env.NODE_ENV || 'development'; |
Access to .env file
| 372 | apiKey: process.env.DEEPGRAM_API_KEY_DEV!, |
Access to .env file
| 373 | projectId: process.env.DEEPGRAM_PROJECT_ID_DEV!, |
Access to .env file
| 377 | apiKey: process.env.DEEPGRAM_API_KEY_STAGING!, |
Access to .env file
| 378 | projectId: process.env.DEEPGRAM_PROJECT_ID_STAGING!, |
Access to .env file
| 382 | apiKey: process.env.DEEPGRAM_API_KEY_PRODUCTION!, |
Access to .env file
| 383 | projectId: process.env.DEEPGRAM_PROJECT_ID_PRODUCTION!, |
External URL reference
| 86 | baseUrl: 'http://localhost:3000', |
External URL reference
| 103 | baseUrl: 'https://staging.example.com', |
External URL reference
| 120 | baseUrl: 'https://api.example.com', |
External URL reference
| 352 | { url: 'https://static.deepgram.com/examples/nasa-podcast.wav' }, |
External URL reference
| 457 | - [Deepgram Projects](https://developers.deepgram.com/docs/projects) |
External URL reference
| 458 | - [API Key Management](https://developers.deepgram.com/docs/api-key-management) |
External URL reference
| 459 | - [Environment Best Practices](https://developers.deepgram.com/docs/environments) |