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

@tjalve/qube-core

v0.2.1

Published

Shared QUBE product, provider, review, and adapter contracts.

Readme

@tjalve/qube-core

Shared provider-neutral contracts for the QUBE package family: work items, review forge surfaces, gate evidence, agent host profiles, and adapter boundaries.

Product CLIs such as @tjalve/aie, @tjalve/aib, and adapter packages depend on this package at runtime. Most users install it transitively through @tjalve/aie, @tjalve/qube, or an adapter install.

For the full QUBE package family and command deck, see https://zark.github.io/ai-qube/ or the repository landing-page artifact at https://github.com/ZarK/ai-qube/blob/HEAD/docs/index.html.

Install

npm install --save-exact --ignore-scripts @tjalve/[email protected]

Adapter and executor installs usually pull this package automatically:

npm install --save-exact --ignore-scripts @tjalve/[email protected] @tjalve/[email protected] @tjalve/[email protected]

Requirements

  • Node.js 24 or newer

Contract modules

Shared provider-neutral QUBE contracts live in focused source modules. The package root index.ts is a public re-export surface only; new contracts should be owned by a focused module first, then exported once from the root.

Contract Ownership

  • json_value.ts: JsonValue, JsonObject.
  • provider_source.ts: provider resource identity and source normalization.
  • work_item_key.ts: provider-neutral work item keys and key helpers.
  • work_item.ts: work item shape, checklist parsing, work item normalization, and issue-number helpers.
  • action_plan.ts: provider-neutral action plan shapes and action-plan helpers.
  • work_provider.ts: work provider capabilities, executor policy, and provider interface.
  • gate_evidence.ts: gate definitions, gate evidence, and evidence normalization.
  • review_item.ts: review item, merge blocker, conversation, feedback, and review-thread resolution contracts.
  • review_forge.ts: review forge provider, review request, lane publishing, and review finding contracts.
  • review_participant.ts: configured review participant coordination and rollup helpers.
  • agent_host.ts: agent host profiles and host review-runner capability contracts.
  • review.ts: compatibility barrel only; do not add contract definitions here.

Keep product-specific policy and runtime behavior in product packages such as @tjalve/aie. QUBE core should stay provider-neutral and should not duplicate type definitions across modules.