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

@phala/pi-provider-aci

v0.7.2

Published

Vendor-neutral Pi provider for private-ai-gateway using an instance-scoped verified ACI transport

Readme

@phala/pi-provider-aci

Vendor-neutral Pi provider for an Attested Confidential Inference (ACI) gateway. It establishes an instance-scoped verified connection with @phala/aci-verifier, injects the scoped transport into Pi, discovers models, verifies every inference receipt before stream completion, and exposes attestation, receipt, and session audit commands.

pi install npm:@phala/pi-provider-aci
export ACI_BASE_URL=https://gateway.example/v1
pi

In Pi, store the gateway key and save a default model through the native UI:

/login aci
# paste the API key and wait for the footer to show aci-verified
/model
# search for aci/, select a model, and press Ctrl+S

Pi owns all persistence: credentials are stored in ~/.pi/agent/auth.json, refreshed catalogs in ~/.pi/agent/models-store.json, and a default selected with Ctrl+S in ~/.pi/agent/settings.json. The cached catalog remains available offline. ACI_API_KEY is also supported for the current process, but Pi does not copy environment variables into its credential store.

The provider fails closed when workload or channel verification fails. For a production reviewed-release claim, configure ACI_ACCEPTED_COMPOSE_HASHES with the comma-separated compose hashes published by the deployment operator. Model capabilities come only from the gateway catalog. Pi reasoning levels use the gateway's public normalized reasoning field; upstream model dialects are handled by the gateway, not by this extension. Pi requires numeric rates for every token category, so an omitted cache rate is represented at the ordinary input rate rather than as a free cache operation.

/aci-receipts lists retained exchanges. /aci-receipt [id] displays or re-verifies the latest or selected exchange's signed receipt, exact wire body hashes, and cited attested session. /aci-session <id> fetches the public session artifact over the pinned connection and validates it locally; it does not require an inference API key.

The local wire-digest history retains the latest 32 receipt-bearing requests by default and is cleared when Pi exits. Credential, model-catalog, and default-model persistence are independent of that audit history. Gateway receipt and session artifacts remain subject to the deployment's server-side retention policy.

See the full client documentation for configuration, trust boundaries, and branded packages.