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

@totems/evm

v1.0.11

Published

Totems EVM smart contracts for building modular token systems

Readme

@totems/evm

Solidity contracts and SDK for building Totems mods.

Full Documentation | Website

Installation

npm install @totems/evm

Or with Foundry:

forge install nsjames/totems-evm

Package Structure

@totems/evm/
  mods/        - TotemMod base contract & TotemsLibrary
  interfaces/  - ITotems, IMarket, ITotemTypes, etc.
  contracts/   - Core contracts (Totems, ModMarket, etc.)
  constants/   - Network addresses
  test/        - Test helpers (TypeScript)
  validator/   - Mod validation tool

Mod Validator

Validates that mod contracts follow the setup pattern correctly.

CLI Usage

# Validate a single contract
npx @totems/evm validate ./contracts/MyMod.sol

# Validate all contracts in a directory
npx @totems/evm validate ./contracts/

# Strict mode - treat warnings as errors (for CI)
npx @totems/evm validate ./contracts/ --strict

# Output as JSON
npx @totems/evm validate ./contracts/ --json

# Generate required actions for market publish
npx @totems/evm validate ./contracts/MyMod.sol --actions

What It Checks

  1. isSetupFor Analysis - Does your mod need setup? If isSetupFor depends on state variables, setup is required.

  2. Setup Functions - Finds functions that modify state used by isSetupFor.

  3. Validator Functions - Each setup function should have a corresponding validator:

    • setAcceptedToken()canSetAcceptedToken()
    • configure()canConfigure()
    • setup()canSetup()
  4. Access Control - Setup functions should have access control (e.g., onlyCreator).

Example Output

────────────────────────────────────────────────────────────
Contract: MinerMod
File: ./contracts/Miner.sol

  isSetupFor: Depends on state
    └─ Variables: totemsPerMine

  Setup Functions:
  ┌─────────────────────────┬─────────────────────────┬─────────────┐
  │ Function                │ Validator               │ Access      │
  ├─────────────────────────┼─────────────────────────┼─────────────┤
  │ setup                   │ canSetup() ✓            │ onlyCreator │
  └─────────────────────────┴─────────────────────────┴─────────────┘

  Result: PASS ✓

Programmatic Usage

import { validateContract, formatResults } from '@totems/evm/validator';

const results = validateContract('./contracts/MyMod.sol');
console.log(formatResults(results));