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

@odradekk/vera-scheme-sandbox

v1.1.0

Published

Chez Scheme WASM sandbox for Vera agent — platform-independent Scheme evaluation

Readme

vera-scheme-sandbox

Purpose

Provide platform-independent Chez Scheme evaluation for Vera through a WASM runtime, with bounded execution and explicit host-filesystem access modes.

Registered surface

Tools

  • scheme_eval — evaluates R6RS/Chez Scheme code; output is captured from (display ...), (printf ...), stderr, and the tool footer.

Commands

  • none

Hooks

  • session_start — verifies the bundled WASM artifacts and warns if integrity checks fail.

Access modes

  • readonly (default) mounts the current working directory at /work and blocks writes under that mount; process spawning is disabled.
  • write mounts the current working directory at /work with read/write access; process spawning is disabled.
  • fullaccess mounts the host root filesystem at /host, keeps the normal process environment, and enables Chez Scheme system().

/work and /host

/work is the session working directory projected into the WASM filesystem for readonly and write runs. Use it for project-local reads, and request write only when the Scheme code needs to create or modify files in that working tree.

/host is only present in fullaccess mode and maps to / on the host. Use it only for tasks that genuinely require whole-host paths or system().

Integrity checks

On session_start, the extension computes sha256 hashes for scheme.js, scheme.wasm, and scheme.data. A mismatch, missing file, or unreadable artifact triggers a warning that scheme_eval may not work correctly; the tool still registers before the check runs.

Smoke

  • npm run smoke
  • from package root: node ./scripts/smoke.mjs

The smoke script exercises arithmetic, recursion, macros, readonly reads, readonly write blocking, write-mode writes, fullaccess host reads, fullaccess system(), and blocked spawning outside fullaccess.

Intended use cases

  • readonly: inspect project files, run pure calculations, test Scheme snippets, and do safe read-only analysis.
  • write: generate or transform project-local files when the requested output should be written under the current working directory.
  • fullaccess: perform trusted host-level inspection or shell-backed Scheme tasks that cannot be completed through /work.

Loaded through agent/settings.json as ./packages/vera-scheme-sandbox.