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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@adorsys-gis/message-pickup

v1.0.2

Published

A library for implementing services to support the retrieval of messages from DIDComm agents via mediators.

Readme

Message Pickup

A library for implementing services to support the retrieval of messages from DIDComm agents via mediators.

Features

| Protocol | Description | Status | | --------------------------------------------------------------- | -------------------------------- | -------------- | | DIDComm Message Pickup | Pick up messages from mediators. | ✅ Implemented |

Installation

To install the library, run the following command:

npm install @adorsys-gis/message-pickup

Usage

Prerequisites

Before using the library, you'll need a DID address for the sending party. This can be created using the DIDIdentityService from the peer library @adorsys-gis/multiple-did-identities. Here's an example of generating a DID using that library:

export const generateIdentity = async (secretPinNumber: number) => {
  const createEvent = waitForEvent(DidEventChannel.CreateDidIdentity);

  didIdentityService.createDidIdentity(
    DIDMethodName.Peer,
    secretPinNumber,
    PeerGenerationMethod.Method2,
  );

  const data = (await createEvent) as ServiceResponse<{ did: string }>;
  return data.payload.did;
};

Using the MessagePickupService

The MessagePickupService is designed to work seamlessly with an event bus architecture. Here's how to pick up messages from a mediator:

import { MessagePickupService } from '@adorsys-gis/message-pickup';
import { MessagePickupEvent } from '@adorsys-gis/message-pickup';

const messagePickupService = new MessagePickupService(
  eventBus,
  secretPinNumber,
);

// Listen on the MessagePickupEvent.MessagePickup event
const channel = waitForEvent(MessagePickupEvent.MessagePickup);
await messagePickupService.ReceiveMessages(mediatorDid, aliceDid);

// Wait for an acknowledgement on MessagePickupEvent.MessagePickup
const eventData = await channel;
console.log('Received event data:', eventData);

Using the MessagePickup Class Directly

If your application does not use an event bus, you can interact directly with the MessagePickup class:

import { MessagePickup } from '@adorsys-gis/message-pickup';

const messagePickup = new MessagePickup(
  didRepository,
  secretPinNumber,
  messageRepository,
);
const messageCount = await messagePickup.processStatusRequest(
  mediatorDid,
  aliceDidForMediator,
);
console.log('Message count:', messageCount);

Additional Help

For more examples and detailed scenarios, consider referring to the test cases in the project.

Contributing

Contributions are welcome! Please feel free to submit a pull request or open an issue for any enhancements or bug fixes. For contribution guidelines, please refer to the CONTRIBUTING.md file.

License

This project is licensed under the MIT License - see the LICENSE file for details.