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

@intentic/graph

v1.413.0

Published

The desired-state representation the deploy tool passes between stages: refs, secrets and readiness checks compiled into one serializable, dependency-ordered graph.

Readme

graph

The desired-state representation the deploy tool passes between stages: refs, secrets and readiness checks compiled into one serializable, dependency-ordered graph.

flowchart LR
    config["deploy.config.ts<br/>env('KEY')"] --> resolver["state-resolver<br/>RawNode[]"]
    resolver -- "compile" --> dsg(["graph<br/>DesiredStateGraph"])
    dsg -- "desired-state.json" --> engine["engine<br/>linearize · hashInputs"]
    dsg -- "collectSecretUsage" --> cli["cli<br/>deploy secrets"]
  • A resource node is { id, type, inputs, dependsOn, readyWhen }. Inside inputs, a dependency's output is { $ref: "id.output" } and a secret is { $secret: { source, key } }, so the artifact is plain JSON with no values filled in.
  • compile derives dependsOn from every ref a node carries and throws on a ref to an unknown id. linearize orders nodes topologically with declaration order as the tiebreak, so apply order is deterministic.
  • Secrets come from env("KEY"), which the user supplies, or generated("KEY"), which intentic creates and stores. Configs import env from this package directly.
  • stamp.ts is the ownership contract: providers label live resources with intentic.id and a hash of their inputs, which lets the engine find and diff them without a state file. Since 2026-10-05 they also carry intentic.owner, the graph's owner (an intent id resolve mints once), and ownershipOf answers whose a stamped resource is: mine, theirs, or unowned (stamped before owners existed). Two intents sharing a host or a zone tell their resources apart by it.
  • A node's type is an opaque string here; resources owns the list of kinds.

Key files

  • src/types.ts — Ref, SecretRef, RawNode, ResourceNode, DesiredStateGraph, Move.
  • src/compile.ts — raw nodes to the serialized graph with derived dependencies.
  • src/index.ts — env, generated, httpOk, linearize, subgraph.
  • src/stamp.ts — the intentic.id, intentic.owner and intentic.hash stamps, and who a stamp belongs to.
  • src/secrets.ts — every secret the graph requires and which nodes need it.

Commands

pnpm --filter @intentic/graph test