npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

neo-decompiler-web

v0.9.0

Published

TypeScript wrapper for the Neo decompiler WebAssembly bindings

Readme

Neo Decompiler Web Package

This folder contains the publishable npm package for the Rust crate compiled to WebAssembly. It adds a thin TypeScript wrapper over the wasm bindings so browser code gets a stable, typed API without duplicating the decompiler logic.

Build

From this directory:

npm install
npm run build:wasm

That runs wasm-pack build .. --target web --out-dir web/dist/pkg --features web --no-default-features followed by scripts/prepare-wasm-package.mjs, generating the wasm glue under web/dist/pkg/.

Then build the TypeScript wrapper:

npm run build:ts

For a full package build:

npm run build:package

Serve

From this directory:

python3 -m http.server 4173

Then open http://localhost:4173.

JS API

import {
  init,
  initPanicHook,
  infoReport,
  disasmReport,
  decompileReport,
} from "neo-decompiler-web";

await init();
initPanicHook();

const info = infoReport(nefBytes, {
  manifestJson,
  strictManifest: false,
});

const disasm = disasmReport(nefBytes, {
  failOnUnknownOpcodes: false,
});

const decompile = decompileReport(nefBytes, {
  manifestJson,
  strictManifest: false,
  failOnUnknownOpcodes: false,
  inlineSingleUseTemps: true,
  outputFormat: "all",
});

nefBytes should be a Uint8Array. manifestJson should be a UTF-8 JSON string.

The wrapper accepts camelCase JS options and translates them into the snake_case ABI expected by the wasm bindings. The published npm tarball includes the compiled TypeScript wrapper plus the wasm artifacts under dist/pkg/.