security-bun

Audit Bun.js applications for shell injection, SQL injection, and insecure server configurations.

124|12|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/IgorWarzocha/Opencode-Workflows --skill security-bun-igorwarzocha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-bun
Source: https://github.com/IgorWarzocha/Opencode-Workflows/tree/main/agents/security-reviewer/.opencode/skill/security-bun
Command: npx skills add https://github.com/IgorWarzocha/Opencode-Workflows --skill security-bun-igorwarzocha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers identify and mitigate common security vulnerabilities specific to the Bun.js runtime environment, preventing potential exploits and data breaches.

Core Features & Use Cases

  • Vulnerability Scanning: Detects risks like shell injection, SQL injection, path traversal, and insecure server configurations.
  • Code Auditing: Provides specific patterns and examples for common Bun security pitfalls.
  • Use Case: Before deploying a new Bun.js application, run this Skill to audit your codebase for critical vulnerabilities such as insecure Bun.spawn() usage or unvalidated file access.

Quick Start

Run the security scan script to audit the current directory for Bun security issues.

Frequently Asked Questions about security-bun

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan Bun.js applications for security vulnerabilities?

To scan Bun.js applications for security vulnerabilities, run an audit script that uses ripgrep to search TypeScript and JavaScript files for dangerous patterns in shell injection, SQL injection, and insecure server configurations, providing actionable insights.

What common security vulnerabilities affect Bun.js runtime environments?

Common Bun.js security vulnerabilities include shell injection from dangerous `$` usage, SQL injection through `sql()` calls, path traversal via unvalidated `Bun.file()` access, and insecure server configurations involving network bindings.

How do I detect insecure Bun.spawn usage in my TypeScript codebase?

Detect insecure `Bun.spawn()` usage in your TypeScript codebase by executing a code audit script that utilizes ripgrep to scan for dangerous shell execution patterns and provides a hardening checklist for mitigation.

Does this Bun.js security scanner require any external dependencies?

This Bun.js security scanner requires no external dependencies, utilizing ripgrep internally to audit TypeScript and JavaScript files for dangerous patterns and insecure server configurations.

What is the best way to prevent shell injection in Bun.js applications?

Prevent shell injection in Bun.js applications by auditing code for dangerous `$` usage and `Bun.spawn()` patterns, then applying a hardening checklist to mitigate identified risks before deployment.