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

@newton-xyz/policy-pack-shared

v0.4.4

Published

Shared TypeScript contract for Newton policy packs. Defines the PolicyPack<Params, WasmArgs, Secrets> interface that @newton-xyz/newton-shield-sdk consumes.

Vulnerabilities

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

Links

Git

Maintainers

jhwon0820jhwon0820albert.brownalbert.brown

Keywords

newtonnewton-protocolpolicy-packshieldvaultcurator

Readme

@newton-xyz/policy-pack-shared

The TypeScript contract every Newton policy pack implements. Consumed by @newton-xyz/newton-shield-sdk's createShield(...) to type the curator's chosen pack.

What's in here

  • PolicyPack<TParams, TWasmArgs, TSecrets> — the canonical interface.
  • Deployment, ChainId — types that mirror the per-pack-per-chain entries in the upstream deployments.json.

This package contains no policy code — no zod schemas for specific packs, no encode/decode logic, no on-chain reads. Each per-pack package (@newton-xyz/policy-pack-vaultsfyi, @newton-xyz/policy-pack-chainalysis, …) implements PolicyPack against its own AVS-side artifacts under <pack>/ at the repo root.

Why split this out

So the Shield SDK can depend on the contract without depending on every pack. A curator that integrates VaultsFYI installs @newton-xyz/policy-pack-vaultsfyi and gets that pack's bindings; the SDK never bundles unused packs.

Versioning

Independent of any specific pack. A 0.x minor bump here is breaking for every published pack and the SDK — coordinate carefully. A 0.x patch is non-breaking (added optional fields, JSDoc, internal types).