Versioned security assessment

Report ID: SA-07053F51

6/30/2026, 12:43:13 PM

bun-development security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
bun-development
Version
v2
Maintainer
sickn33
Source
github.com/sickn33/antigravity-awesome-skills/tree/main/skills/bun-development
Coverage
1 Files scanned · 692 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

4 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

The skill is documentation-only and I found no prompt-injection text or confirmed malicious intent. However, high-risk copy-paste examples are present, including remote install scripts piped to shells, PowerShell iex execution, third-party registries, env access, filesystem reads, and package execution commands.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

1 Files scanned · 692 Lines analyzed

4 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 13 evidence locations

Filesystem access

May read or write local files.

Observed in 1 evidence location

Env variables

May read values from the process environment.

Observed in 5 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 74 evidence locations

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (4)

RISK-001 High
SKILL.md:28SKILL.md:31SKILL.md:586
Remote Install Scripts Executed Through Shells
The installation and migration sections instruct users to run remote installer content through bash or PowerShell iex. This is a true positive because copied commands can execute network-delivered code before users inspect it.
The exact pipe-to-shell and iex patterns are present in installation guidance. The content appears legitimate for Bun setup, but the execution pattern is inherently high risk for marketplace users.
RISK-002 High
SKILL.md:147
Non-Standard Package Registry Example
The package management section demonstrates installing from https://registry.npmmirror.com. This is not malicious by itself, but it can route dependency resolution through a third-party registry with different trust and availability properties.
The registry URL is explicitly shown in a package install command. The example has a legitimate purpose, but users need clear review before changing package trust sources.
RISK-003 Medium
SKILL.md:26-42SKILL.md:136-157SKILL.md:157-176SKILL.md:176-191SKILL.md:470-491SKILL.md:580-590SKILL.md:674-682
Broad External Command Guidance
The static analyzer flagged many shell command examples. Most are normal Bun workflows, but they still cause local project changes, install packages, remove dependency folders, run package binaries, or build executables when copied.
The commands are visible documentation examples rather than hidden automation. They are still operational commands with local side effects, so the external-command risk is real but contextual.
RISK-004 Medium
SKILL.md:238-245SKILL.md:250SKILL.md:528SKILL.md:572
Environment Variable and Env File Handling
The skill explains automatic .env loading and shows API key and database URL access. This is legitimate Bun guidance, but it touches secrets and should warn users not to expose or log sensitive values.
The cited lines explicitly reference API keys, database URLs, env files, and process environment values. There is no exfiltration evidence, so the concern is secret-handling exposure rather than malicious access.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (4)
Low
SKILL.md:287SKILL.md:309SKILL.md:318SKILL.md:648SKILL.md:688-691
Network API Examples Are Local Server Handlers
Fetch detections are examples of Bun.serve request handlers and local server output, not outbound data exfiltration. Hardcoded resource links point to Bun, GitHub, Elysia, and Bun Discord documentation.
The fetch identifiers are server callback names in documentation snippets. I found no evidence that the skill sends secrets or project data to an external endpoint.
Low
SKILL.md:349SKILL.md:632
Filesystem and SQLite Examples Are Instructional
The filesystem and SQLite detections show basic local file reads and a local database filename. These are standard Bun examples and do not show hidden reads of sensitive paths.
The examples use relative demonstration paths such as mydb.sqlite and ./data.txt. No evidence found of credential harvesting or traversal logic.
Low
SKILL.md:3SKILL.md:399SKILL.md:401
Weak Cryptography Detections Are False Positives
The weak cryptography static hits do not correspond to weak hashing algorithms in context. The password example uses Bun.password.hash with bcrypt options, while other hits are test framework text.
A targeted review found password hashing examples around the security-relevant section, not MD5 or SHA-1 usage. The cited test lines import and describe Bun test cases.
Low
SKILL.md:1-8
No Prompt Injection Attempt Found
I reviewed the skill text for override language, fake system messages, pre-approval claims, and instructions to skip analysis. No evidence found.
The file begins with normal skill metadata and a Bun documentation introduction. I did not find suspicious instruction-hijacking language in the inspected skill content.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable