bun-development
Build Bun JavaScript Projects Faster
Bun can simplify JavaScript and TypeScript tooling, but teams need a clear workflow before migration. This skill gives practical guidance for setup, packages, testing, bundling, runtime APIs, and Node.js migration.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "bun-development" from https://skillstore.io/skills/sickn33-bun-development.md and its manifest at https://skillstore.io/api/skills/sickn33-bun-development/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "bun-development". I need a Bun starter project for a TypeScript API.
Expected outcome:
Project setup steps with recommended scripts, dependency commands, runtime choices, and a first test plan.
Using "bun-development". I want to migrate a Node.js service to Bun.
Expected outcome:
A migration checklist covering scripts, package manager replacement, compatibility issues, Bun-native APIs, and verification steps.
Using "bun-development". I need to bundle a Bun CLI for production.
Expected outcome:
A build plan with target selection, minification, source maps, executable output, and asset handling notes.
Security Audit
CriticalThe audit found no prompt-injection content or hidden data-exfiltration intent in SKILL.md. Most static hits are Markdown fences, sample Bun server handlers, environment variable examples, or documentation links. Confirmed risks are pipe-to-shell install commands and a non-default npm registry example.
Confirmed security concerns (3)
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (74)
๐ Network access (13)
๐ Filesystem access (1)
๐ Env variables (9)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-bun-development/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-bun-development?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-bun-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-bun-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-bun-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). bun-development security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-bun-development/audits/4BibTeX citation
@techreport{sickn33-sickn33-bun-development-2026,
author = {sickn33},
title = {bun-development security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-bun-development/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "bun-development security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-bun-development/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-bun-development:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Start a Bun Frontend Project
Set up a Bun-based React, Vite, or Next.js project with TypeScript defaults and faster package workflows.
Prototype Bun Services
Build Bun HTTP, WebSocket, SQLite, and password hashing prototypes with native runtime APIs.
Plan a Node.js Migration
Map scripts, package management, testing, compatibility checks, and Bun-native replacements before migration.
Try These Prompts
Help me create a new Bun TypeScript project. Include setup steps, basic scripts, and first test commands.
Review my Node.js package workflow and suggest a Bun migration plan for scripts, dependencies, tests, and lockfiles.
Audit this Bun service design and recommend native APIs for file handling, HTTP routing, WebSockets, SQLite, and password hashing.
Create a production Bun build checklist covering bundling, executable targets, source maps, environment files, and deployment risks.
Best Practices
- Verify remote installation scripts before running them, especially pipe-to-shell commands.
- Pin package versions and use trusted registries for reproducible dependency installs.
- Run Bun tests and build checks after changing runtime, bundler, or migration settings.
Avoid
- Piping remote scripts directly into a shell without inspection or checksum verification.
- Switching npm registries globally without confirming trust, availability, and package integrity.
- Assuming every Node.js API behaves identically under Bun without testing edge cases.