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

abel-sdk

v0.1.6

Published

**Abel is an Asset Labeling registry, as well as a provider of batch asset data.**

Readme

Abel SDK for js-algorand-sdk v2

Abel is an Asset Labeling registry, as well as a provider of batch asset data.

Docs site: abel-docs.d13.co

Install

[!WARNING] This version of abel-SDK only supports js-algorand-sdk v2 and its corresponding algokit-utils v7

npm i abel-sdk

Usage

[!NOTE] Want to explore with a CLI? Check out abel-cil which uses this SDK under the hood.

The default use case is with a read-only client. This will allow you to fetch asset and label data, but not operate on the registry.

Create an SDK instance by passing in the abel app ID and an an algokit.AlgorandClient.

For Mainnet:

import { AlgorandClient } from "@algorandfoundation/algokit-utils";
import { AbelSDK } from "abel-sdk";

const abel = new AbelSDK({
  appId: 2914159523n, // Abel Mainnet PoC App ID
  algorand: AlgorandClient.fromConfig({
    algodConfig: { server: "https://mainnet-api.4160.nodely.dev", port: 443 },
  }),
});

Querying assets

You can query assets with multiple size views.

To get the "Asset Micro Labels" view for multiple assets:

const microData = await abel.getAssetsMicro([312769n, 6547014n, 6587142n, 27165954n]);
// returns
// Map(4) {
//   312769n => { id: 312769n, unitName: 'USDt', decimals: 6n, labels: [ 'pv' ] },
//   6547014n => { id: 6547014n, unitName: 'MCAU', decimals: 5n, labels: [ 'pv' ] },
//   6587142n => { id: 6587142n, unitName: 'MCAG', decimals: 5n, labels: [ 'pv' ] },
//   27165954n => { id: 27165954n, unitName: 'Planets', decimals: 6n, labels: [ 'pv' ] }
// }

The available asset views are:

To fetch asset data in these views, use the corresponding getXYZ method of the SDK, e.g. getAssetMicroLabels.

You can pass in as many asset IDs as you want.

Performance

Under the hood, Abel uses simulate to fetch multiple assets' data from a single simulate call.

The number of assets per simulate request depends on how many AVM resources are required to compose it.

You will get the best performance and efficiency if you use the smallest possible view for your needs.

128 assets per simulate call

64 assets per simulate call

42 assets per simulate call

Concurrency

The Abel SDK supports arbitrarily large asset lookups.

If you request more assets than a single simulate call can provide for that view, parallel simulate requests will be made in order to fetch your data.

By default, Abel will use up to 4 simulate "threads", i.e. it will keep up to 4 simulate requests in parallel in order to fetch asset data.

You can control this level of concurrency by passing in a concurrency property in the Abel SDK constructor.

[!NOTE] The concurrency limit is per-method call, not global. For example, if you have concurrency: 2 and you await two separate getAssetsTiny() methods of more than 128 assets each, there will be 4 simulate requests in flight.

Admin or Operator Usage

To instantiate the SDK with write capabilities, pass in your privileged account as writeAccount:

import { AlgorandClient } from "@algorandfoundation/algokit-utils";
import { AbelSDK } from "abel-sdk";

const mnemonic = "apple apple ...";
const writeAccount = await algorand.account.fromMnemonic(mnemonic);

const abel = new AbelSDK({
  appId: 2914159523n, // Abel Mainnet PoC App ID
  algorand: AlgorandClient.fromConfig({
    algodConfig: { server: "https://mainnet-api.4160.nodely.dev", port: 443 },
  }),
  writeAccount,
});

You can then operate on your label group, as well as any asset:

const someAddress = "DTHIRTEENNLSYGLSEXTXC6X4SVDWMFRCPAOAUCXWIXJRCVBWIIGLYARNQE";
const labelId = "13"
// add another operator to your label
await abel.addOperatorToLabel(someAddress, labelId);

// remove operator from your label
await abel.removeOperatorFromLabel(someAddress, labelId);

// add label to asset with ID 1013
await abel.addLabelToAsset(1013n, labelId);

// remove label from asset with ID 1013
await abel.removeLabelFromAsset(1013n, labelId);