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

pve-sdk

v1.0.2

Published

A typed SDK for interfacing with the Proxmox VE API.

Readme

pve-sdk

A typed SDK for interfacing with the Proxmox VE API. Includes code for generating this SDK from the API specification. This version was generated against Proxmox VE 9.2.5.

Usage

The SDK is structured identically to PVE's API paths, with types also sourced from the API specification. Supported authentication methods are API tokens (recommended) or password/TOTP with automatic ticket renewal.

import PVE from 'pve-sdk';

const client = new PVE({
  hostname: 'https://example.com:8006',
  username: 'root@pam',
  tokenId: 'my-token',
  tokenSecret: 'aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee',
});
const taskId = await client.nodes.node('my-node').qemu.createVm({ vmid: 100 });
const taskStatus = await client.nodes.node('my-node').tasks.upid(taskId).status.readTaskStatus();
console.info(taskStatus.status);

Building from API specification

Copy the PVE API specification to src/apidoc.json. This can be sourced from /usr/share/pve-docs/api-viewer/apidoc.js on an up-to-date PVE installation. The start of the new file should look something like this:

[
  {
    "children": [
      {
        "children": [
          {
            "info": {
              "DELETE": {
                "allowtoken": 1,
                "description": "Mark replication job for removal.",
                "method": "DELETE",
                "name": "delete",

Then, run pnpm i and pnpm run generate to generate index.ts.