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

@veris-ai/veris-sim-opencode

v0.7.0

Published

Test an application against Veris - stateful twins of the external services it calls. Three commands: setup (wire a repo once), build <issue|prompt> (measure the vendor before designing, prove the change through veris-proxy), fix <issue|prompt> (reproduce

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ali-verisali-verismjameimjameivictorshihvictorshih

Keywords

opencodeopencode-pluginverisintegration-testingsandboxmcp

Readme

@veris-ai/veris-sim-opencode

Veris for OpenCode: three engineer-invoked commands plus the veris MCP server. Veris runs stateful twins of the external services an application calls; veris-proxy reroutes the application's outbound HTTP(S) into a sandbox from outside the process, so the code under test keeps its production hostnames, credentials and client stack, and ends each run with a receipt of what the sandbox received.

Install

opencode plugin @veris-ai/veris-sim-opencode -g

(or add "@veris-ai/veris-sim-opencode" to the plugin array in ~/.config/opencode/opencode.json). Then export your credential and restart opencode:

export VERIS_API_KEY=<key>

VERIS_API_BASE overrides the control plane (defaults to https://svc.api.veris.ai). Until the key is set, opencode mcp list shows the veris server as failed; the commands still run and setup walks you through it.

Commands

| command | what it does | |---|---| | /veris-sim:setup | wires the repository to a Veris environment, once — credential, environment, transport, one smoke run with proof of arrival | | /veris-sim:build <issue link \| prompt> | measures every vendor claim the task rests on against the twin before designing, proves the change through veris-proxy with a receipt | | /veris-sim:fix <issue link \| prompt> | reproduces the failure the issue describes before designing, proves the same failure closed with a receipt |

The commands are plain OpenCode commands: only the engineer can start them, the model cannot invoke them on its own.

Source and the shared skill files: https://github.com/veris-ai/plugins