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

@mutants/cardano

v1.20.3

Published

This library is an alternative to the cardano-serialization-lib and does not require your app to load WebAssembly code.

Readme

Mutants Cardano BETA

This library is an alternative to the cardano-serialization-lib and does not require your app to load WebAssembly code.

Sample transaction

In this transaction, the seller is sending a Mutant Croc NFT to our Marketplace validator, including a datum.

import {
  UTXOS,
  AssetUtils,
  RequiredInputs,
  RequiredOutputs,
  TransactionBuilder,
} from "@mutants/cardano";

// This is the asset the seller is going to send to our validator.
const mutantCrocAsset = {
    unit: "d517f38dd2c5acc3347c8e933e2c0185fafe3ba838f8830000a3c95f44724361726f6e6f566163696e75733030303030",
    quantity: "1" 
};

const estimateFee = 500000;
const sellerAddress = "addr1..." // Here you define the NFT seller payment address

// Here we calculate the min ADA required to be attached to the NFT
const minAdaUtxo = UTXOS.calculateMinMultiassetCost(
    AssetUtils.fromAssetsToPolicyMap([mutantCrocAsset])
);

// Here we define the seller required inputs. In order to send the NFT to the validator, we need to consume the NFT utxo,
// so we add the token, the min ADA that needs to be attached to it and an estimate fee (fee will be recalculated later)
const requiredInputs: RequiredInputs = {
    [sellerAddress]: {
        totalCoin: requiredUtxoADA + estimateFee,
        tokens: inputToken,
    },
};

// Here we define the required outputs. Since we want to send our NFT to our validator, we use the validator address here
// and determine that an output should be created with the Mutant NFT asset plus the minimum ADA required to be attached to that NFT.
// We also add the datum here, that will be used in our Plutus validator.
// In this case the datum has only 2 fields but ofc this would change depending in your validator script.
const datum = {
    constructor: 0,
    fields: [
      {
        bytes: seller,
      },
      {
        int: price,
      }
    ]
};

const requiredOutputs: RequiredOutputs = {
    [validator.address]: {
        totalCoin: minAdaUtxo,
        tokens: [mutantCrocAsset],
        datum,
    },
};