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

@incident-io/pulumi

v0.4.1

Published

A Pulumi package for managing incident.io resources.

Readme

Pulumi provider for incident.io

Manage incident.io configuration as code from a Pulumi program, in TypeScript, Python or Go.

Generated from terraform-provider-incident, so anything you can manage with Terraform you can manage here.

Install

npm install @incident-io/pulumi
pip install pulumi-incident
go get github.com/incident-io/pulumi-incident/sdk/go/incident

Configure

Create an API key in Settings → API keys, then either:

pulumi config set --secret incident:apiKey inc_...
# or
export INCIDENT_API_KEY=inc_...

On a dedicated or self-hosted deployment, also set incident:endpoint.

Example

import * as incident from "@incident-io/pulumi";

const trivial = new incident.Severity("trivial", {
    name: "Trivial",
    description: "Issues causing no impact.",
    rank: 1,
});

Per-resource reference and examples in all three languages are on the Pulumi Registry page.

What you can manage

Escalation paths, schedules and schedule sync rules. Alert sources, routes and attributes. Catalog types, attributes and entries. Severities, statuses, incident roles, custom fields. Workflows, maintenance windows, policies, secrets and API keys.

Resources with Beta in the name track features still changing in the product, and their inputs may change in a minor release.

Import existing configuration

Every resource supports pulumi import:

pulumi import incident:index/severity:Severity trivial 01ABCDEF...

Importing claims the resource as managed by code, which stops it being edited in the dashboard. That claim is a write to your account, so set markImportedResourcesAsManaged to false if you would rather imports left it untouched.

Moving from the Terraform bridge

If you use pulumi package add terraform-provider incident-io/incident today, this package replaces it. Resource names and properties are the same, so your program does not change. Remove the packages entry from Pulumi.yaml, delete the generated SDK, and install the published package.

Help

CONTRIBUTING.md covers building and regenerating the SDKs.

MIT licensed. See LICENSE.