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

@polyscope/sdk

v0.1.0

Published

Official Polyscope SDK for JavaScript and TypeScript

Downloads

30

Readme

Polyscope JS SDK

A TypeScript/JavaScript SDK for the Polyscope API.

Installation

npm install @polyscope/sdk

Quick Start

import { Polyscope } from "@polyscope/sdk";

const polyscope = new Polyscope({ apiToken: "your-api-token" });

const servers = await polyscope.servers();
const repositories = await polyscope.repositories();
const workspaces = await polyscope.workspaces();

// Create a workspace directly from a repository resource.
const workspace = await repositories[0].createWorkspace({
  prompt: "Fix the login flow",
  serverId: "srv-1", // optional
});

// Or use a prompt string shorthand.
const workspace = await repositories[0].createWorkspace("Fix the login flow");

If no token is passed, the SDK automatically falls back to Polyscope's local settings file and reads authToken. By default it checks:

  • ~/.polyscope/settings.json
  • ~/Library/Application Support/com.getpolyscope.app/settings.json
  • ~/.config/com.getpolyscope.app/settings.json
  • %APPDATA%/com.getpolyscope.app/settings.json

You can override this with:

POLYSCOPE_SETTINGS_PATH=/custom/path/settings.json

If you need a custom base URL:

const polyscope = new Polyscope();
polyscope.setBaseUrl("https://your-polyscope-instance.com");
polyscope.setApiToken("your-api-token");

Supported API Areas (v1 only)

  • Servers: servers()
  • Repositories: repositories()
  • Workspaces: workspaces(), createWorkspace(), workspace(), deleteWorkspace()
  • Workspace messages: workspace.messages(), workspace.prompt()
  • Workspace actions: workspace.diff(), workspace.commit(), workspace.pullRequest(), workspace.stop()

Error Handling

The SDK maps common HTTP/API failures to typed errors:

  • ValidationError
  • AuthenticationError
  • ForbiddenError
  • NotFoundError
  • RateLimitError
  • ServerOfflineError
  • ServerTimeoutError
  • ApiError

Example:

import { Polyscope, ValidationError } from "@polyscope/sdk";

try {
  await polyscope.createWorkspace({ repositoryId: "" });
} catch (error) {
  if (error instanceof ValidationError) {
    console.log(error.errors);
  }
}

Development

npm run build
npm run typecheck