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-statement-graph

v0.0.3

Published

Source-trusted finalized service and datalake descriptor views

Downloads

102

Readme

Service Kit Statement Graph adapter

Publish-ready B2 service and datalake views. This adapter is separate from the published B1 content-only packages and is not installed in existing consumers. See the B2 contract and verified implementation status.

Public API

resolveFinalizedDescriptor(query, options) accepts:

  • A service identity (chain, provider, service ID) or data-lake identity (chain, operator, lake ID), plus exact at: { block, hash } target pins.
  • One explicitly trusted FinalizedChainSource with chainId(), block.blockByNumber() and finalization.headNumber() viewer methods.
  • Explicit B1 seed readers; optional total/replay/body limits and caller signal.

FinalizedDescriptorQueryZod validates caller pins. Invalid queries or configuration throw before source/reader I/O. The package does not export a shortcut that blesses arbitrary records or imported checkpoints as finalized.

The source must return native hydrated blocks: a Block Bound Witness and its committed payloads, including transactions and same-block elevated Claim carriers. SDK root hashes, chain/height, previous links and target consistency are checked. Consensus and signature validation remain the source's trust responsibility; structurally valid signed-looking objects alone are not proof.

Outcomes

| Status | Meaning | | --- | --- | | active | The unique latest started revision is unexpired at the target. Only this status is selectable. | | pending | No revision has started; the pending root is reported. | | expired | The latest started revision expired; an older revision is not restored. | | absent | Complete replay and body resolution found no matching identity under this contract. | | conflicted / invalid | The complete identity history has competing roots/successors or broken lineage/evidence. No selected descriptor. | | incomplete | Missing bodies/history, changed pins, source errors, or work limits prevented a complete answer. No selected descriptor. | | aborted | The caller cancelled the operation. No selected descriptor. |

Complete results carry immutable source-trusted-finalized-replay provenance: source and chain identity, exact target, observed finalized head, fold version, and fixed schema policy. A service/lake Claim requires both source and subject to equal the pinned provider/operator. Body hashes and strict shapes are checked through B1, with no recursive references or advertised URL fetching.

An unavailable eligible body can belong to any identifier under the authority; it makes the query incomplete. An exact-hash body proven invalid for its declared schema can be discarded, with a count in the result. Profile support, prices, access grants and endpoint safety are separate consumer checks.

Limits and release boundary

Default replay starts at genesis and permits 4,096 blocks, 8,192 applied records and 256 eligible objects within 30 seconds. Per-block JSON and source deadlines also apply, as do B1's body limits. Large histories intentionally return incomplete; authenticated baselines/resumption are not implemented. Parsed-object limits do not enforce network wire limits, and source/readers that ignore cancellation may continue I/O after the resolver stops waiting.

The prepared package uses the public Statement Graph 0.5.2 and XL1 protocol 5.5.0 baselines. It remains unqualified as registry-consumable until its owner publishes 0.0.2 and the clean consumer passes against that registry artifact. Do not claim anonymous installation based on an offline packed check from a populated cache. Local fixture tests do not qualify live consensus, native HTTP, browser use, Sequence, Mainnet or hosted operation. Receiver mailboxes remain deferred.