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

@bun-win32/amsi

v1.0.1

Published

Zero-dependency, zero-overhead Win32 AMSI bindings for Bun (FFI) on Windows.

Readme

@bun-win32/amsi

Zero-dependency, zero-overhead Win32 AMSI bindings for Bun on Windows.

Overview

@bun-win32/amsi exposes the amsi.dll exports using Bun's FFI. It provides a single class, Amsi, which lazily binds native symbols on first use. You can optionally preload a subset or all symbols up-front via Preload().

The Antimalware Scan Interface (AMSI) lets an application submit arbitrary content — scripts, buffers, downloaded payloads — to the registered antivirus provider (Windows Defender by default) for in-process scanning, with no temp files and no shelling out. It is the same pipeline PowerShell, WScript, and Office use.

The bindings are strongly typed for a smooth DX in TypeScript.

Features

  • Bun-first ergonomics on Windows 10/11.
  • Direct FFI to amsi.dll (in-process malware scanning via the registered AV provider).
  • In-source docs in structs/Amsi.ts with links to Microsoft Docs.
  • Lazy binding on first call; optional eager preload (Amsi.Preload()).
  • No wrapper overhead; calls map 1:1 to native APIs.
  • Strongly-typed Win32 aliases (see types/Amsi.ts).

Requirements

  • Bun runtime
  • Windows 10 or later

Installation

bun add @bun-win32/amsi

Quick Start

import Amsi, { AMSI_RESULT } from '@bun-win32/amsi';

const ctxBuf = Buffer.alloc(8);
if (Amsi.AmsiInitialize(Buffer.from('MyApp\0', 'utf16le').ptr, ctxBuf.ptr) === 0) {
  const ctx = ctxBuf.readBigUInt64LE(0);

  const result = Buffer.alloc(4);
  const content = Buffer.from('console.log("hello")\0', 'utf16le');
  Amsi.AmsiScanString(ctx, content.ptr, Buffer.from('snippet\0', 'utf16le').ptr, 0n, result.ptr);

  const code = result.readInt32LE(0);
  const isMalware = code >= AMSI_RESULT.AMSI_RESULT_DETECTED;
  console.log(isMalware ? 'BLOCK' : 'allow', `(AMSI_RESULT=${code})`);

  Amsi.AmsiUninitialize(ctx); // always pair with AmsiInitialize
}

[!NOTE] AI agents: see AI.md for the package binding contract and source-navigation guidance. It explains how to use the package without scanning the entire implementation.

Examples

Run the included examples:

bun run example/malware-scanner.ts
bun run example/amsi-diagnostic.ts

Notes

  • Either rely on lazy binding or call Amsi.Preload().
  • Always pair AmsiInitialize with AmsiUninitialize, and AmsiOpenSession with AmsiCloseSession.
  • result is an out-pointer to an AMSI_RESULT (Int32): use AmsiResultIsMalware semantics — code >= AMSI_RESULT_DETECTED (32768) means block.
  • Windows only. Bun runtime required.