๐Ÿ“ฆ

wasm-rust

์ฝ˜ํ…์ธ  ๋ฆฌ๋น„์ „ r1 ์•ˆ์ „ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด๐ŸŒ ๋„คํŠธ์›Œํฌ ์ ‘๊ทผ

Build Rust WebAssembly Modules for the Browser

Compute-heavy browser workloads can suffer from JavaScript processing costs and frequent data transfers. This skill guides Rust WebAssembly integration and optimization based on measured bottlenecks.

์ง€์›: Claude Codex Code(CC)
Maintain this Skill? Claim it ๐Ÿฅ‰ 78 ๋ธŒ๋ก ์ฆˆ

๋‚ด ์—์ด์ „ํŠธ๋กœ ์„ค์น˜

์ด ์š”์ฒญ์„ ์—์ด์ „ํŠธ์— ๋ณต์‚ฌํ•˜์„ธ์š”. ๊ณต์‹ Skill ํŽ˜์ด์ง€์™€ ๋งค๋‹ˆํŽ˜์ŠคํŠธ๊ฐ€ ํฌํ•จ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ ์š”์ฒญ
Review the Skillstore skill "wasm-rust" from https://skillstore.io/skills/shreyam1008-wasm-rust.md and its manifest at https://skillstore.io/api/skills/shreyam1008-wasm-rust/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

์—์ด์ „ํŠธ๋Š” ๊ณ„์†ํ•ด์„œ ๊ณ„ํš์„ ํ‘œ์‹œํ•˜๊ณ  ๋ณด์•ˆ ์ •์ฑ…์—์„œ ์š”๊ตฌํ•˜๋Š” ํ™•์ธ์„ ์š”์ฒญํ•ด์•ผ ํ•ฉ๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ๊ฐ€ ์ฝ๊ธฐ ์‰ฌ์šด ๋ฆฌ์†Œ์Šค

AI ์—์ด์ „ํŠธ, ํฌ๋กค๋Ÿฌ, ์Šคํฌ๋ฆฝํŠธ๊ฐ€ ์ „์ฒด ํŽ˜์ด์ง€ ๋Œ€์‹  ์ •๋ฆฌ๋œ ์ปจํ…์ŠคํŠธ๋งŒ ํ•„์š”ํ•  ๋•Œ ์ด ๋งํฌ๋ฅผ ์‚ฌ์šฉํ•˜์„ธ์š”.

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"wasm-rust" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Should I move many tiny browser calculations into WASM?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

Frequent small calls can cost more in transfers than they save in computation. Profile first, then consider moving the entire loop into Rust.

"wasm-rust" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Does a mutable Rust byte slice provide zero-copy access to a JavaScript typed array?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • The wasm-bindgen mutable-slice binding copies input into WASM and copies mutations back when the call returns.
  • For zero-copy access, keep ownership in WASM and expose a typed-array view with an explicit lifetime contract.
  • Recreate views after memory growth, and discard them before Rust frees or reallocates the buffer.

"wasm-rust" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. What should I check before enabling shared-memory threads?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • Check that the deployment supplies the required cross-origin opener and embedder isolation headers.
  • Use worker-based execution to keep the main thread responsive.
  • Validate browser support and retain an appropriate fallback when the support contract requires it.

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „

All 29 command findings match Markdown formatting, not Ruby or shell backtick execution. The URL finding is a documentation link without data transmission instructions. No evidence found of prompt injection, credential access, exfiltration, or unrelated destructive actions.

1
์Šค์บ”๋œ ํŒŒ์ผ
106
๋ถ„์„๋œ ์ค„ ์ˆ˜
0
๊ฒ€ํ†  ํ•ญ๋ชฉ
0
์˜คํƒ ๋ฌด์‹œ๋จ
๊ฐ€์žฅ ์ตœ๊ทผ์— ์™„๋ฃŒ๋œ ์ •์ ยท์˜๋ฏธ๋ก ์  ๊ฐ์‚ฌ์—์„œ ํ™•์ธ๋œ ๋ณด์•ˆ ๋ฐœ๊ฒฌ ์‚ฌํ•ญ์ด ๊ฐ์ง€๋˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค. ์ด๋Š” ์Šคํ‚ฌ์— ๋ถ€์ž‘์šฉ์ด ์—†์Œ์„ ์ฆ๋ช…ํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.
๊ฐ์‚ฌ์ž: codex
์ด ๋ณด๊ณ ์„œ ๊ณต์œ  ๋ฐ ์ธ์šฉ

๋ฒ„์ „์ด ์ง€์ •๋œ ํ‰๊ฐ€ ๋ณด๊ณ ์„œ, ์ค‘๋ฆฝ ๋ฐฐ์ง€, ์ž„๋ฒ ๋“œ ์นด๋“œ ๋ฐ ์ธ์šฉ์„ ๊ณต์œ ํ•˜์„ธ์š”. Skillstore๋Š” ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ•˜์ง€๋งŒ ์ด Skill์˜ ์•ˆ์ „ ์—ฌ๋ถ€๋ฅผ ํŒ๋‹จํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.

๋ฒ„์ „๋ณ„ ๋ณด๊ณ ์„œ ์—ด๊ธฐ
๋ณด์•ˆ ํ‰๊ฐ€

๋ณด๊ณ ์„œ ๋งํฌ ๋ณต์‚ฌ

https://skillstore.io/skills/shreyam1008-wasm-rust/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown ๋ฐฐ์ง€

[![Skillstore security assessment](https://skillstore.io/badges/skills/shreyam1008-wasm-rust/security.svg)](https://skillstore.io/skills/shreyam1008-wasm-rust?utm_source=security_passport_badge)

HTML ๋ฐฐ์ง€

<a href="https://skillstore.io/skills/shreyam1008-wasm-rust?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/shreyam1008-wasm-rust/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

์ž„๋ฒ ๋“œ ์นด๋“œ

<iframe src="https://skillstore.io/embed/skills/shreyam1008-wasm-rust.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
ํ•™์ˆ  ์ธ์šฉ (APA ยท BibTeX ยท CFF)

APA ์ธ์šฉ

shreyam1008. (2026). wasm-rust security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-wasm-rust/audits/1

BibTeX ์ธ์šฉ

@techreport{shreyam1008-shreyam1008-wasm-rust-2026, author = {shreyam1008}, title = {wasm-rust security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/shreyam1008-wasm-rust/audits/1}, 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: "wasm-rust security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "shreyam1008" date-released: "2026-10-02" url: "https://skillstore.io/skills/shreyam1008-wasm-rust/audits/1" identifiers: - type: other value: "skillstore:shreyam1008-wasm-rust:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore ์ ์ˆ˜

์ด ์ ์ˆ˜์˜ ์ด์œ  ์ฆ๊ฑฐ ์‹ ๋ขฐ๋„: ์ค‘๊ฐ„
55
์•„ํ‚คํ…์ฒ˜
85
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
65
์ปค๋ฎค๋‹ˆํ‹ฐ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Move browser computation into Rust

Evaluate and package a measured image-processing or simulation kernel while keeping browser interactions in JavaScript.

Reuse Rust computation in a web application

Expose an existing numeric Rust routine through wasm-bindgen and choose the appropriate wasm-pack packaging target.

Reduce JavaScript and WASM transfer overhead

Review typed-array transfers, call frequency, worker placement, and SIMD or threading prerequisites before optimizing.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Assess a first WASM workload
Use wasm-rust to assess whether my browser task suits WebAssembly: [task]. Explain transfer costs, required tools, and reasons to keep JavaScript.
Create a minimal browser module
Use wasm-rust to create a minimal numeric Rust module for [operation]. Include crate configuration, wasm-bindgen exports, wasm-pack commands, and JavaScript initialization.
Review typed-array transfers
Use wasm-rust to review my typed-array integration: [implementation]. Identify copies, recommend coarse calls, and define lifetime rules for any WASM-owned buffers.
Plan measured runtime optimization
Use wasm-rust to analyze [profile] for [browser targets]. Propose worker placement, SIMD experiments, threading prerequisites, package optimization, and fallbacks. Separate measured facts from hypotheses.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Profile representative workloads and measure transfer overhead before selecting or optimizing WASM.
  • Keep computation calls coarse and define ownership rules for buffers shared through typed-array views.
  • Keep bindings and tool versions compatible, and verify browser features and deployment headers before enabling advanced execution.

ํ”ผํ•˜๊ธฐ

  • Move trivial or DOM-heavy tasks into WASM without measuring whether computation outweighs integration costs.
  • Treat mutable-slice bindings as zero-copy, or retain views after buffer reallocation or memory growth.
  • Assume SIMD or shared-memory threads work across all browsers and deployments without compatibility checks.

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

Which AI tools can use this skill?
The marketplace lists support for Claude, Codex, and Claude Code. Rust compilation requires a separate local toolchain.
Does WebAssembly always run faster than JavaScript?
No. Small tasks and frequent transfers can erase computational gains. Profile the complete workload before choosing WASM.
What does wasm-pack generate?
The build produces a WASM module, JavaScript bindings, and TypeScript declarations. The packaging target determines how applications import the output.
Are JavaScript typed-array transfers zero-copy?
Standard slice bindings copy data. Zero-copy views require WASM-owned memory and explicit lifetime rules, including view recreation after memory growth.
What do shared-memory threads require?
They require compatible tooling and browser support, plus cross-origin isolation headers. Verify the deployment before relying on threaded execution.
Can this skill implement GPU rendering or DOM styling?
Those tasks are outside its scope. WASM targets CPU computation; GPU pipelines need WebGPU tooling, and DOM work uses JavaScript or browser bindings.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

shreyam1008

๋ผ์ด์„ ์Šค

MIT

Skillstore ๋ฆฌ๋น„์ „

r1

๋ฒ„์ „ ์•ˆ๋‚ด

์ž‘์„ฑ์ž๊ฐ€ ๋ฒ„์ „์„ ์„ ์–ธํ•˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค.

์ฐธ์กฐ

bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5

์œ ์ง€๋ณด์ˆ˜ ์ตœ์‹ ์„ฑ

2026. 10. 2.

์‚ฌ์šฉ๋Ÿ‰

0 ๋‹ค์šด๋กœ๋“œ ยท 0 ์กฐํšŒ

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md