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

forgedoe

v1.0.12

Published

a very light typescript wrapper around the forgejo http api

Readme

forgedoe

"for forgejo does"

this is a very light typescript wrapper around the forgejo http api

it uses the openapi/swagger spec, forgejo version 16.0.3+gitea-1.22.0

source code available on git at https://git.vixen.computer/era/forgedoe

how to use it

install

npm install forgedoe # or your preferred package genre

instantiate with an access token

import { createClient } from 'forgedoe';

const forgejo = await createClient("YOUR.FORGEJO.HOST", {
  kind: 'token',
  token: process.env.YOUR_ACCESS_TOKEN
});

instantiate with username and password

import { createClient } from 'forgedoe';

// Note that Basic Auth is more dangerous (it cannot be scoped) but is required for certain endpoints (e.g. deleting an access token from a user)
const forgejo = await createClient("YOUR.FORGEJO.HOST", {
  kind: 'basic',
  username: 'doof',
  password: process.env.YOUR_PASSWORD,
});

now you can fetch with awesome intellisense !!!

examples

type await forgejo.fetch(' and all available endpoints will populate typescript autosuggest

type await forgejo.fetch('/some/endpoint', ' and the available methods for the given endpoint will populate

type await forgejo.fetch('/some/endpoint', 'method', {}) and the object will have the proper type enforced for the given query. the response object will be typed as a discriminated union of the possible response bodies for each possible http status code

const response = await forgejo.fetch('/repos/{owner}/{repo}/branches', 'post', {
  path: { owner: 'doof', repo: 'projectinator' },
  body: { new_branch_name: 'feature/self-destruct-button' },
});

if (response.status == 201) {
  // Now response.body is properly typed as
  // {
  //   commit: {
  //     added: string[];
  //     author: {
  //       email: string;
  //       name: string;
  //       username: string;
  //     };
  //     committer: {
  //       email: string;
  //       name: string;
  //       username: string;
  //     };
  //     id: string;
  //     message: string;
  //     modified: string[];
  //     removed: string[];
  //     timestamp: string;
  //     url: string;
  //     verification: {
  //       payload: string;
  //       reason: string;
  //       signature: string;
  //       signer: {
  //         email: string;
  //         name: string;
  //         username: string;
  //       };
  //       verified: boolean;
  //     };
  //   };
  //   effective_branch_protection_name: string;
  //   enable_status_check: boolean;
  //   name: string;
  //   protected: boolean;
  //   required_approvals: number;
  //   status_check_contexts: string[];
  //   user_can_merge: boolean;
  //   user_can_push: boolean;
  // };
}

caveats

for endpoints that return binary data, response.body will be an ArrayBuffer containing said data, but will have type unknown. i should fix this probably.

i think this should also work with CommonJS require but idk

attribution

hoof-made with <3 by era 𐂂 in vancouver, canada

thx to all forgejo contributors for making awesome open source software

thx to https://vixen.computer/ for hosting this project and the forgejo instance it was built for