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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@arcjet/redact-wasm

v1.0.0-alpha.30

Published

Arcjet sensitive information redaction detection engine

Downloads

2,972

Readme

@arcjet/redact-wasm

Arcjet sensitive information redaction detection engine.

Installation

npm install -S @arcjet/redact-wasm

Example

import { initializeWasm } from "@arcjet/redact-wasm";
import type { SensitiveInfoEntity } from "@arcjet/redact-wasm";

function noOpDetect(_tokens: string[]): Array<SensitiveInfoEntity | undefined> {
  return [];
}
function noOpReplace(_input: SensitiveInfoEntity): string | undefined {
  return undefined;
}

const wasm = await initializeWasm(noOpDetect, noOpReplace);

// If WebAssembly isn't available in the environment then it will be undefined.
if (typeof wasm !== "undefined") {
  const config = {
    entities: [],
    contextWindowSize: 1,
    skipCustomDetect: true,
    skipCustomRedact: true,
  };

  const entities = wasm.redact("I am a string", config);
  // Do something with entities that should be redacted.
} else {
  throw new Error(
    "redact failed to run because Wasm is not supported in this environment",
  );
}

Implementation

This package provides sensitive information identification and redaction logic implemented as a WebAssembly module which will run local analysis on the provided string.

The generated _virtual/arcjet_analyze_bindings_redact.component.js file contains the binary inlined as a base64 Data URL with the application/wasm MIME type.

This was chosen to save on storage space over inlining the file directly as a Uint8Array, which would take up ~3x the space of the Wasm file. See Better Binary Batter: Mixing Base64 and Uint8Array for more details.

It is then decoded into an ArrayBuffer to be used directly via WebAssembly's compile() function in our entry point file.

This is all done to avoid trying to read or bundle the Wasm asset in various ways based on the platform or bundler a user is targeting. One example being that Next.js requires special asyncWebAssembly webpack config to load our Wasm file if we don't do this.

In the future, we hope to do away with this workaround when all bundlers properly support consistent asset bundling techniques.

License

Licensed under the Apache License, Version 2.0.