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

@siredmar/semantic-release-kandji

v1.1.0

Published

This provides a semantic-release plugin for updating artifacts for Kandji custom apps

Readme

semantic-release-kandji

A semantic-release plugin for managing custom apps in Kandji, allowing you to automate the upload of assets and updating of custom app configurations during the release process.

Features

  • Upload assets (e.g., binaries, zip files) to Kandji custom apps.
  • Update the postinstall_script of a custom app if provided.
  • Supports both pre-releases and full releases, configurable via plugin options.

Requirements

  • Node.js: Ensure you have Node.js installed.
  • Environment Variables:
    • KANDJI_BASE_URL: The base URL for the Kandji API.
    • KANDJI_API_TOKEN: The API token for authenticating with Kandji.

Installation

Install the plugin from npm:

npm install --save-dev @siredmar/semantic-release-kandji

Configuration

Add the plugin to your .releaserc.json file with the required options:

{
  "branches": ["main"],
  "plugins": [
    [
      "@siredmar/semantic-release-kandji",
      {
        "appID": "myappid",
        "asset": "/path/to/asset.zip",
        "preRelease": true,
        "release": true,
        "postinstall_script": [
          "#!/bin/bash",
          "cp /usr/local/bin/myconf.conf $HOME/.myapp/myconf.conf"
        ]
      }
    ]
  ]
}

Options

| Option | Type | Required | Description | |----------------------|------------|----------|-----------------------------------------------------------------------------| | appID | string | Yes | The ID of the custom app to update in Kandji. | | asset | string | Yes | The path to the asset file to upload. | | preRelease | boolean | No | Indicates whether the plugin should run on pre-releases. Default: false. | | release | boolean | No | Indicates whether the plugin should run on full releases. Default: true. | | postinstall_script | string[] | No | An optional post-install script to add to the custom app configuration. |

Usage

When semantic-release runs, the plugin will:

  1. Validate the plugin configuration and required environment variables.
  2. Check if the asset file exists.
  3. Upload the asset to Kandji using the Kandji API.
  4. Update the custom app configuration, including the postinstall_script (if provided).

Example Workflow

  1. Add the plugin to .releaserc.json.
  2. Ensure the environment variables KANDJI_BASE_URL and KANDJI_API_TOKEN are set.
  3. Push a release commit.
  4. Semantic-release will automatically upload the asset and update the app in Kandji.

Environment Variables

Ensure the following environment variables are set:

  • KANDJI_BASE_URL: Your Kandji API base URL (e.g., https://your-instance.api.kandji.io).
  • KANDJI_API_TOKEN: Your API token for Kandji.

You can use a .env file for local development:

KANDJI_BASE_URL=https://your-instance.api.kandji.io
KANDJI_API_TOKEN=your_api_token

Debugging

To enable detailed debugging logs, set the DEBUG environment variable:

DEBUG=semantic-release:kandji

Testing

You can run the plugin locally with a simulated context:

(async () => {
  const config = {
    appID: "your-app-id",
    asset: "/path/to/asset.zip",
    preRelease: false,
    release: true,
    postinstall_script: [
      "#!/bin/bash",
      "cp /usr/local/bin/myconf.conf $HOME/.myapp/myconf.conf"
    ]
  };

  const context = {
    branch: { prerelease: false },
    logger: console
  };

  try {
    await kandjiSemanticReleasePlugin(config, context);
  } catch (error) {
    console.error("Error:", error.message);
  }
})();

License

This project is licensed under the MIT License.