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

@atlasprotocol/types

v0.2.0

Published

Shared TypeScript type definitions for the ATLAS Protocol — events, ticket types, manifests, purchase challenges, W3C VC receipts, and IPFS pinner abstractions.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nooblemon_ethnooblemon_eth

Keywords

atlasatlas-protocoltypesschemas

Readme

@atlasprotocol/types

Shared TypeScript type definitions for the ATLAS Protocol. This is a pure-types package — no runtime code, no schema validators, no dependencies beyond typescript itself.

What lives here

  • AtlasEvent and supporting interfaces (AtlasEventLocation, AtlasEventOrganizer, AtlasEventAvailability, AtlasEventStatus, AtlasPriceRange)
  • AtlasTicketType and supporting interfaces (AtlasFee, AtlasPricing, AtlasTicketAvailability, AtlasTicketRestrictions, AtlasCancellationPolicy)
  • AtlasManifest and supporting interfaces
  • AtlasPurchaseChallenge, AtlasPaymentMethod, AtlasPaymentMethodType, AtlasPaymentProof
  • AtlasReceipt (W3C VC shape), AtlasReceiptCredentialSubject, AtlasReceiptSettlement, AtlasReceiptProof, ReceiptPaymentMethod
  • Pinner, PinOptions, PinResult, FetchLike — IPFS pinning service abstraction

Why a separate package

@atlasprotocol/server-sdk and @atlasprotocol/ipfs both need these shapes. Without a shared types package, the two SDKs would form a workspace dependency cycle (server-sdk imports Pinner from ipfs; ipfs imports AtlasEvent from server-sdk). Lifting the pure type definitions into this package lets each SDK depend only on @atlasprotocol/types, which depends on nothing.

Install

pnpm add @atlasprotocol/types

Most consumers will not need this directly — @atlasprotocol/server-sdk and @atlasprotocol/ipfs re-export everything they consume from here for back-compat.

Adoption

The protocol types in this package are the canonical definitions consumed across the SDK:

  • @atlasprotocol/server-sdk imports AtlasEvent, AtlasTicketType, AtlasManifest, AtlasPurchaseChallenge, AtlasReceipt, and Pinner from here. Existing imports from @atlasprotocol/server-sdk keep working because server-sdk re-exports the same types — both paths resolve to the identical declarations, so they are mutually assignable.
  • @atlasprotocol/ipfs imports AtlasEvent (consumed by generateEventCid) and the Pinner / PinOptions / PinResult / FetchLike interfaces from here. The four bundled pinner implementations (PinataPinner, Web3StoragePinner, FilebasePinner, KuboPinner) all implement the canonical Pinner from @atlasprotocol/types.
  • @atlasprotocol/connector-framework imports AtlasEvent and AtlasTicketType from here directly.

New consumer code can import from @atlasprotocol/types directly; old code that imports the same names from @atlasprotocol/server-sdk or @atlasprotocol/ipfs continues to compile unchanged.