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

@kosha-ai/integration-basic

v0.5.2

Published

Basic-auth integration for Kosha: any API behind a username and password

Readme

@kosha-ai/integration-basic

Any API behind HTTP Basic auth.

Unlike every other integration there is no provider here: the operator gives a base URL per configuration, the end user gives a username and password, and Kosha proxies with Authorization: Basic base64(username:password).

import { basic } from '@kosha-ai/integration-basic';

export default defineConfig({
  integrations: [basic()],
});

Rename the two fields where the API calls them something else:

basic({
  credentialFields: [
    { key: 'username', label: 'Email', type: 'string', required: true },
    {
      key: 'password',
      label: 'API token',
      type: 'string',
      required: true,
      secret: true,
    },
  ],
});

What it does not do

No identity. An arbitrary API has no endpoint meaning "this credential is good", so nothing is checked at connect and a wrong password surfaces on the first proxied call. The connection is labelled with the username because that is the only identity available.

No refresh. A password does not expire on a schedule anyone can see.

The base URL

Operator-supplied and called by the server, so it is checked on every proxied request: https only, and refused if the hostname resolves to a loopback, link-local, private or carrier-grade NAT address. Checked per request rather than only when saved, since a hostname that answers publicly today can answer privately tomorrow.