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

@pollar/accessly-adapter

v0.10.0-rc.8

Published

Accessly Smart Account wallet adapter for @pollar/core — sign Stellar transactions with a user's Accessly C-address (passkey + MPC) smart wallet, client-side.

Readme

@pollar/accessly-adapter

Accessly Smart Account adapter for @pollar/core. Lets a user sign Stellar transactions with their Accessly Smart Account (a C-address Soroban contract secured by passkey + Shamir-MPC), client-side.

Smart, but client-signed

Accessly is a self-custodial smart wallet: Accessly deploys and manages the C-address contract, and the user signs via Accessly's SDK (passkey unlock → Shamir-reconstructed ed25519 seed). So the adapter reports custody: 'smart', but signing/submitting happens client-side + RPC — Pollar never holds the key and does not deploy/sponsor/submit through wallet-service (that path is only for Pollar's own smart wallets).

Install

npm i @pollar/accessly-adapter @pollar/core @accesly/react @accesly/core

Usage

signRawXdr lives behind Accessly's React hook, so you wire it in your component and hand the adapter a bound signXdr:

import { useAccesly } from '@accesly/react';
import { createAccesslyAdapter } from '@pollar/accessly-adapter';
import { PollarClient } from '@pollar/core';

function makeClient(accesslyAddress: string, username: string) {
  const { wallet, tx } = useAccesly();

  const accessly = createAccesslyAdapter({
    address: accesslyAddress, // the Accessly C-address
    signXdr: async (transactionXdr) => {
      const { ed25519Seed, expectedPublicKey } = await wallet.unlockForSigning(username);
      const { signedXdr } = await tx.signRawXdr({ transactionXdr, ed25519Seed, expectedPublicKey });
      return signedXdr;
    },
  });

  return new PollarClient({
    apiKey: '…',
    walletAdapters: [accessly], // shows an "Accessly" button; login({ provider: 'accessly' })
  });
}

API

createAccesslyAdapter(options): WalletAdapter

| option | type | notes | |---|---|---| | address | string | the Accessly Smart Account C-address | | signXdr | (xdr) => Promise<string> | signs a full XDR via Accessly; returns the signed XDR | | meta? | { label; iconUrl? } | login button; defaults to { label: 'Accessly' } |

⚠️ Pending confirmation

This adapter assumes Accessly's signRawXdr signs an arbitrary Pollar-built XDR for the account. If Accessly only signs txs built by its own SDK (send, swap), Pollar's generic buildTx flow won't apply and Accessly would need to own the transaction flow instead. End-to-end login also requires Pollar's SEP-10 backend to accept contract-account (C-address) authentication.