WASM builds
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust, wasm
- Domain
- build-system, security
Research direction
The issue names no files, tests, or entry points. Start by inspecting the Rust build configuration and attempting a WASM compilation to identify the unknown failures; done means the project builds successfully for WASM with client-side encryption keys.
Written by the indexing model from the issue text.
Description
Encryption must use clientside keys, so ideally, this should be compiled to WASM. I can foresee no reason why it shouldn't, but it doesn't yet compile to WASM for unknown reasons.
- Dominant language
- Rust
- Stars
- 119
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bitmask-stack/carbonado
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitmask-stack/carbonado#31 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitmask-stack/carbonado#28 · 1 comment ·
-
Catalog Format v0May be free again @cryptoquick claimed this 1308 days ago, and no pull request is open. Open
bitmask-stack/carbonado#21 · 1 assignee ·
-
Web Storage ProviderOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
bitmask-stack/carbonado#18 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
bitmask-stack/carbonado#17 ·
All issues in bitmask-stack/carbonado
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
vercel-labs/agent-browser#2017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/turso#9405 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolyMeilex/Neothesia#447 ·
Maintainers usually reply within 1 day
-
backend::vllm diffusion multimodal
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trezor/trezor-firmware#7985 ·
Maintainers usually reply within 2 days