mirror of
https://github.com/Momoko-Ayase/Senbei.git
synced 2026-09-19 03:57:59 -04:00
Momoko-Ayase
512a627066
Dropping an .apk/.apks/.xapk package or a .so library reported "not recognized — will be skipped", which reads as "not protected" when the real gap is that the Android pipeline (filesystem orchestration in senbei-io) has no wasm build. These files now get an explicit android pseudo-kind at staging time: the row explains that the CLI handles them, and they neither enable the Unpack button nor error out mid-run.
Senbei Web
Senbei runs in the browser through the senbei-wasm crate. Files are read locally, unpacked in a worker, and offered back as downloads; no server receives input bytes.
Features
- Protected
.exeand.dllfiles produce<name>.unpack.*downloads. - External
.exe._and.dll._companions are paired by filename. global-metadata.datproducesglobal-metadata.unpack.datwhen tokens change.- Each output receives the same static integrity check as the CLI.
Every unpack uses a disposable Web Worker so a WebAssembly trap cannot freeze the page. A trapped DLL can be retried through the forced-EXE path, matching native routing.
Build
cd senbei-wasm
wasm-pack build --target web --release --out-dir ../web/pkg
Serve web/ with a static HTTP server, for example python -m http.server -d web 8000. Opening index.html with file:// does not work because browser modules require HTTP.
Layout
senbei-wasm/src/lib.rs contains the bindings. web/app.js manages the dropzone and downloads, web/worker.js runs one unpack job per worker, and web/pkg/ contains ignored wasm-pack output.