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

@clawnify/knowledge

v0.1.0

Published

Read your organization's Company Knowledge from a deployed Clawnify app.

Readme

@clawnify/knowledge

Read your organization's Company Knowledge from a deployed Clawnify app, so the app does not ask its user to retype what the org already wrote down.

import { offering } from "@clawnify/knowledge";

// In a server route, before an AI call that needs to know what the org sells.
const settings = await getSettings(c.env);
const pinned = settings.about ? null : await offering(c.env);
const about = settings.about || pinned?.body || "";

offering(env) returns the document the org pinned as "what we sell" in Settings → Brand, or null:

| Returns | When | |---|---| | { id, title, version, published_at, body, url } | A published document is pinned | | null | No token (the app runs outside Clawnify), nothing pinned, or the pinned document is a draft, archived, or flagged outdated | | throws ClawnifyKnowledgeError | The call failed (unauthorized, network_error, redirect_refused, …) |

null means "fall back to your own field", which is why an open-source app keeps its settings field: deployed anywhere else, the field is the only source. Treat the app's own field as an override when it is filled, and show where the text comes from when it is not (Per ${title} v${version}, linking to url).

Configuration

CLAWNIFY_TOKEN is injected into every app Clawnify deploys. Never expose it in browser code. An OAuth bearer also works, with optional CLAWNIFY_ORG_ID to select the organization. CLAWNIFY_API_URL overrides the HTTPS origin; localhost HTTP is allowed for development.

The token is one per organization and shared by its apps, so a pinned document is readable by every app in the org. Only documents pinned for apps are served.