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

@suss/intent-ir

v0.33.1

Published

The types for the intent your team writes down, product outcomes and system behavior, in a shape suss can check the code against.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mattkindymattkindy

Keywords

sussstatic-analysisintentprdspecificationtypescript

Readme

@suss/intent-ir

Part of suss, which reads both sides of every call in a repository and says where the two disagree.

The team-authored side of the loop: what the code was meant to do, in a form that pairs against the derived BehavioralSummary of what it does.

What this package is

Two citizens, discriminated by kind, both built on @suss/ir-core so intent and behaviour describe boundaries the same way:

  • System intent (kind: boundary): what one boundary should do, as named outcomes. The boundary is REST, function-call, message-bus, storage or unit-invocation, and every field of one comes off the @suss/ir-core schema for that protocol.
  • Outcome intent (kind: prd): human when / expect scenarios, each with an optional link to a system-intent outcome (<intent-name>.<outcome-id>). A scenario with no link is a valid state to be in: it reads fully, and nothing has linked it to an outcome yet.

Where it fits in suss

It is a peer of @suss/behavioral-ir; both build on @suss/ir-core. Readers (e.g. @suss/contract-intent) parse files into IntentDoc and call intentDocToSummary; the checker pairs the result against derived code summaries.

Status

v0: REST, function-call, message-bus, storage and unit-invocation system intent, effects as outcomes, PRD outcome intent with optional links. GraphQL, runtime-config and metric boundaries have no block yet.

The file format is also published as a JSON Schema, generated from the zod schemas at build time, so an editor can check a document and a tool in another language can read one without depending on this package. Intent format goes through both document kinds field by field.

More

Coverage

coverage

License

Apache-2.0