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

@xyo-network/service-kit-xl1

v0.2.1

Published

Configured public XL1 datalake seeds for Service Kit

Readme

@xyo-network/service-kit-xl1

Creates an explicitly configured readonly Service Kit seed through the native XL1 REST datalake viewer.

The current public release is 0.1.0, published October 1, 2026 and registry rechecked October 5. It depends on XL1 SDK ~5.8.4. Earlier native HTTP and packed/registry-consumer receipts remain version-specific; publication does not qualify current native/browser behavior, consumer adoption or hosted availability. This datalake adapter does not supply B2's chain reader. See implementation status and the B3 contract.

The checkout declares Node ^26: SDK Protocol 8.0.3 confines the selected graph to that major, and XL1 SDK 5.8.4 admits Node >=26. Development/CI and current qualification use Node 26.9.0; other Node 26 versions require their own recorded qualification. This corrects the former adapter Node >=22.3 declaration and root Node 24.14.1 pin. Published 0.1.0 metadata remains unchanged until release; older runtime receipts remain historical. Browser outputs and the configured-reader contract are unchanged. See implementation status for the current local packed gate and its limits.

import { createXl1DataLakeSeed } from '@xyo-network/service-kit-xl1'

const seed = await createXl1DataLakeSeed({
  id: 'public-control-lake',
  endpoint: 'https://lake.example/dataLake',
  endpointPolicy: 'public-https',
})

Every read forces credentials omit and redirect error, forwards the B1 attempt signal, and maps the B1 body cap to the native decoded-response cap. The adapter accepts no token, signer, headers, writer or discovered locator.

Public endpoints require HTTPS. Use explicit-local only when the host has deliberately allowed a local HTTP deployment. The host still owns DNS, resolved-address, port, decompression and egress policy.