wasmtime-auditor

Audit Wasmtime source code to discover bugs and security vulnerabilities.

18.6k|1.8k|Updated Aug 29, 2017
One-click install
npx skills add https://github.com/bytecodealliance/wasmtime --skill wasmtime-auditor-bytecodealliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wasmtime-auditor
Source: https://github.com/bytecodealliance/wasmtime/tree/main/.agents/skills/wasmtime-auditor
Command: npx skills add https://github.com/bytecodealliance/wasmtime --skill wasmtime-auditor-bytecodealliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security auditing a large WebAssembly runtime like Wasmtime requires deep domain knowledge, systematic exploration, and reproducible evidence. This Skill guides an AI agent through a disciplined audit of the Wasmtime codebase to find new, undiscovered bugs and vulnerabilities. ## Core Features & Use Cases - Structured Bug Hunting: Defines what counts as a valid bug (issues reachable through the public wasmtime crate API or CLI), prioritizing Tier 1 and Tier 2 features. - Reproducible Test Cases: Requires every finding to include a runnable proof, either as a .wast test file or a Rust crate depending on wasmtime. - Organized Reporting: Produces numbered bug report folders and intermediate findings under a reports/ directory with system info, commit version, and audit date. - Use Case: A security researcher asks the agent to audit Wasmtime's table implementation; the agent explores the code, builds a failing .wast reproduction, and writes reports/001-table-oom/report.md. ## Quick Start Audit the Wasmtime codebase in this repository for new security bugs and write reproducible reports into the reports folder.

Frequently Asked Questions about wasmtime-auditor

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

FAQPage Schema
How do I audit Wasmtime for security vulnerabilities?

Audit Wasmtime by reviewing its source code for logic errors reachable through the public wasmtime crate API or CLI, then proving each finding with a runnable test case. Prioritize Tier 1 and Tier 2 features, which carry the highest security impact.

What counts as a valid bug in a Wasmtime audit?

A valid bug must be triggerable through Wasmtime's public API or CLI, not through private types. It can be a security vulnerability or even a debug_assert failure, but it must be new, undiscovered, and demonstrated by a working test case.

How do I write a reproducible test case for a Wasmtime bug?

Write a .wast test file with CLI flags noted in comments, or a small Rust crate that depends on the wasmtime crate and drives the runtime to trigger the bug. The test must actually exercise Wasmtime, not just demonstrate a general programming concept.

Can Wasmtime bugs be platform-specific?

Yes, bugs can be specific to operating systems or host architectures. Cross-architecture testing with QEMU on Linux helps uncover issues that only appear on other platforms.

Where are Wasmtime audit results stored?

All results go in a reports folder at the repository root. Each bug gets a numbered folder like reports/001-table-oom containing report.md and test artifacts, while intermediate findings go in reports/findings/.