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

@oxy.so/allo-sdk

v1.0.0

Published

Two entries, each importable on its own:

Readme

Allo SDK

Two entries, each importable on its own:

  • @oxy.so/allo-sdk/links — links into Allo (start a direct conversation, hand Allo something to send) for any Oxy app. No dependencies.
  • @oxy.so/allo-sdk/server — the managed-team snapshot read, for backends. Requires @oxy.so/core >=7 <8 (an optional peer: the root and /links entries never load it).

The root entry re-exports /links and the TeamSnapshot type.

Reading a team snapshot

import { alloTeamForOxyService } from '@oxy.so/allo-sdk/server';

const team = alloTeamForOxyService(oxy); // the process's one OxyServer
const snapshot = await team.snapshot(capability); // TeamSnapshot | null

Every request carries two things, and neither replaces the other:

  • The caller's Oxy service token — transport identity. It is minted by OxyServer.createServiceClient for Allo's audience (SERVICE_AUDIENCE, oxy-service:<Allo's application id>) from the process's attested workload identity (Oxy ADR 0026/0049). No API key, internal scope or app consent is involved.
  • The team's capability (x-allo-team-capability) — the resource grant. Membership and operation checks are Allo's, whoever the caller is.

snapshot answers null when the capability names no team, and throws for any other refusal (a missing or inactive service identity, an outage), so an authentication failure is never read as "no team".

createServiceClient mints from workload identity only, so the read is open to Oxy-attested workloads. An OxyServer configured only with serviceAuth (an external application's API key pair) has no workload identity to mint from, so its snapshot reads fail; there is no second, key-based path.

1.0.0 — the snapshot read always authenticates

0.x exported AlloTeamAccessClient, whose default constructor called the snapshot route with bare fetch and no token. That client is gone, so Allo can require a service token on the route.

  • Removed: the AlloTeamAccessClient class and its root export. Its shape survives as the AlloTeamAccessClient interface in /server.
  • Unchanged: alloTeamForOxyService(oxy), SERVICE_AUDIENCE, the TeamSnapshot type and everything in /links.

A backend that already used alloTeamForOxyService only bumps the version.