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

@nevermined-io/protocol-artifacts

v1.5.0

Published

Typed ABIs and addresses of the deployed Nevermined protocol contracts

Readme

@nevermined-io/protocol-artifacts

Typed ABIs and addresses of the deployed Nevermined protocol contracts. Built and published by nevermined-io/protocol on every release, so consumers never compile the contracts repo.

import {
  nvmConfigAbi,     // ABI, `as const`
  nvmConfigAddress, // address
  nvmConfigConfig,  // { address, abi }
  addresses,        // { NVMConfig: '0x…', … }
  manifest,         // { version, gitSha, addressesSource, networks }
} from '@nevermined-io/protocol-artifacts'

A few interfaces that consumers call on addresses they get at runtime ship as an ABI only, with no address: iFeeControllerAbi (a plan's fee controller can be any IFeeController).

Plain JSON is also exported: @nevermined-io/protocol-artifacts/abis/<Contract>.json, /addresses.json and /manifest.json.

One address set

The contracts are deployed with CREATE2, so they have the same address on every network. manifest.networks lists the networks (name → chainId). The build fails if any network disagrees, so the package never ships two address sets.

Versions

| Package version | Addresses from | npm dist-tag | |---|---|---| | X.Y.Z (release) | deployments/deployment-vX.Y.Z-<network>.json, every network required | latest | | X.Y.Z-rc.N, X.Y.Z-dev.<sha> (prerelease) | deployments/latest-<network>.json (last deploy) | rc, dev |

manifest.addressesSource is release or latest accordingly. Each version is published together with the nvm-local-chain image of the same tag (vX.Y.Z), so a consumer pins both to one release.

Building it locally

forge build
pnpm build:artifacts                  # -> dist/protocol-artifacts, version <package.json>-local
node scripts/artifacts/build-package.mjs --version 1.6.0 --out /tmp/pkg
node scripts/artifacts/build-package.mjs --self-test

To try an unreleased contract change from nvm-monorepo, build it here and pnpm link the dist/protocol-artifacts directory there.

See scripts/artifacts/build-package.mjs for the full rules and .github/workflows/release-artifacts.yml for the release job.