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

@giveusaproject/addon-kit

v1.1.0

Published

Build add-ons for Give Us a Project: define tools, lists, schedules and views, and test them on practice data.

Readme

@giveusaproject/addon-kit

The add-on kit for Give Us a Project. Build add-ons that put a card on Home, add a page to the sidebar, give Archie (the app's assistant) a new tool, or run a job on a schedule, and test them on practice data before anyone turns them on.

Most people start with the command-line tool, which creates an add-on folder that already uses this kit:

npx @giveusaproject/addon-cli create my-addon

What's in it

| Import | For | |---|---| | @giveusaproject/addon-kit | defineBundle, defineTool, defineCollection, defineHook, defineSuggestion, defineSettings, defineView and the types they use | | @giveusaproject/addon-kit/server | what server code gets: context types, errors (ValidationError, NotFoundError, …), permission helpers | | @giveusaproject/addon-kit/client | React for views: AddonProvider, useCollection, useTool, useSlotContext, usePreferences, useAnnounce, … | | @giveusaproject/addon-kit/ui | components that look like the app (Card, EmptyState, Stack, …); import @giveusaproject/addon-kit/ui/styles.css once | | @giveusaproject/addon-kit/testing | createTestContext: practice data (empty, small-team, busy-sprint) and the same isolate the app runs add-on code in |

A tool, a view and a test

// server/index.ts
import { defineBundle, defineTool } from "@giveusaproject/addon-kit";
import { z } from "zod";

export const waitingTasks = defineTool({
  id: "waiting_tasks",
  description: "See bundle.md",
  parameters: z.object({ projectId: z.string().uuid() }),
  effect: "read",
  async handler(args, ctx) {
    const page = await ctx.tickets.list({ projectId: args.projectId, limit: 200 });
    return page.items.filter((t) => t.status.category === "blocked").map((t) => t.key);
  },
});

export default defineBundle({ id: "@my-team/waiting", tools: [waitingTasks] });
// ui/main.tsx
import "@giveusaproject/addon-kit/ui/styles.css";
import { AddonProvider, useTool } from "@giveusaproject/addon-kit/client";
import { Card } from "@giveusaproject/addon-kit/ui";
// tests/addon.test.ts
import { createTestContext } from "@giveusaproject/addon-kit/testing";
const ctx = createTestContext({ bundle: addon, permissions: ["tickets:read"], fixtures: "busy-sprint" });

Rules the app enforces

  • Server code runs in a locked-down isolate: no Node built-ins, no network, no other packages. It may import this kit, zod and its own files.
  • Views run in a sandboxed frame and may import react, react-dom/client, this kit's /client and /ui, and their own files.
  • Every permission the code uses must be listed in bundle.md. People see them before they turn the add-on on, and an admin agrees to anything new in a later version.

Run npx @giveusaproject/addon-cli guide for the full guide (folder layout, bundle.md, checks, uploading, AI coding tools).

Licence

MIT