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

@kernprotocol/sdk

v0.2.0

Published

Official Kern TypeScript SDK

Readme

@kernprotocol/sdk

Official TypeScript SDK for Kern API (Node 18+, fetch-based).

Install

npm install @kernprotocol/sdk

5-minute Quickstart

Set env vars:

export KERN_BASE_URL="https://api.kernprotocol.com"
export KERN_API_KEY="<your-api-key>"

1) Initialize client + create task

import { KernClient } from "@kernprotocol/sdk";

const client = new KernClient({
  baseUrl: process.env.KERN_BASE_URL!,
  apiKey: process.env.KERN_API_KEY!,
});

const created = await client.tasks.create({
  title: "Storefront verification",
  instructions: "Upload one clear photo of the storefront",
  location: { lat: -12.0464, lng: -77.0428, radius_m: 75 },
});

const taskId = created.id ?? created.task_id;

2) Get upload URL

const workerId = "worker-quickstart-001";

const uploadMeta = await client.tasks.getEvidenceUploadUrl({
  taskId,
  workerId,
  contentType: "image/jpeg",
});

// uploadMeta: { upload_url, object_key, expires_in_seconds }

3) Upload file (Node)

import fs from "node:fs/promises";

const bytes = await fs.readFile("./proof.jpg");
const putRes = await fetch(uploadMeta.upload_url, {
  method: "PUT",
  headers: { "Content-Type": "image/jpeg" },
  body: bytes,
});

if (!putRes.ok) throw new Error(`Upload failed: ${putRes.status}`);

4) Upload file (Browser)

// file: File from <input type="file" />
const putRes = await fetch(uploadMeta.upload_url, {
  method: "PUT",
  headers: { "Content-Type": file.type || "application/octet-stream" },
  body: file,
});

if (!putRes.ok) throw new Error(`Upload failed: ${putRes.status}`);

5) Submit evidence

await client.tasks.submitEvidence({
  taskId,
  workerId,
  objectKey: uploadMeta.object_key,
  lat: -12.0464,
  lng: -77.0428,
  timestampIso: new Date().toISOString(),
});

6) Wait for final decision

const finalTask = await client.tasks.waitForFinalDecision({
  taskId,
  timeoutMs: 5 * 60_000,
  pollIntervalMs: 2_000,
});

console.log("Final status:", finalTask.status); // COMPLETED | REJECTED | CANCELED

Core API

new KernClient({ baseUrl, apiKey, timeoutMs?, maxRetries?, retryOnStatuses? })
  • tasks.create(...)
  • tasks.get(taskId)
  • tasks.events(taskId)
  • tasks.getEvidenceUploadUrl(...)
  • tasks.submitEvidence(...)
  • tasks.waitForFinalDecision(...)

Existing worker lifecycle methods are still available (worker.token/claim/start/evidence/complete).

Error handling

SDK throws KernError:

  • status
  • code
  • message
  • requestId (from X-Request-Id response header)
  • details

Backward compatibility: raw remains as a deprecated alias of details.

Retries, timeout, idempotency

  • Default timeout: 20s per request.
  • Retries default to 429/503, with exponential backoff + jitter.
  • Retry-After header is respected when present.
  • Retries are only attempted for safe/idempotent requests:
    • safe methods (GET, HEAD, OPTIONS) OR
    • requests with Idempotency-Key.
  • Unsafe calls should include Idempotency-Key for safe retries.