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

@alejandrocantero/kanbamd

v1.8.0

Published

Manage Kanban boards backed by Markdown files, frontmatter, and column folders.

Readme

@alejandrocantero/kanbamd

TypeScript library and CLI for managing Kanban boards stored as Markdown files with YAML frontmatter in column directories.

Install

npm install @alejandrocantero/kanbamd

Global CLI install

npm install -g @alejandrocantero/kanbamd

Board Layout

Each column is a directory. Each card is a .md file:

board/
├── todo/
│   └── fix-login.md
├── doing/
│   └── refactor-auth.md
└── done/

A card file:

---
title: Fix login
tags: [bug]
order: 1
priority: high
assignee: alice
---
OAuth callback fails when redirect_uri has a trailing slash.

Reserved frontmatter fields (managed by kanbamd, cannot be used as custom fields):

| Field | Type | Description | |---|---|---| | title | string | Card title (required) | | tags | string[] | List of tags | | order | integer | 1-based position within column |

Filesystem metadata is exposed as createdAt (birthtime) and updatedAt (mtime).

SDK

Setup

import { Kanbamd } from "@alejandrocantero/kanbamd";

const board = new Kanbamd({
  root: "./board",
  columns: ["todo", "doing", "done"],
  createRoot: false,       // default: false — create root dir if missing
  createColumns: true,     // default: true  — create column dirs inside root
});

await board.init();

Memory storage

In-memory storage for testing or programmatic use (no filesystem required):

const board = new Kanbamd({
  storage: "memory",
  columns: ["todo", "doing", "done"],
});

await board.init();

Typed custom fields

Pass a type parameter to constrain custom frontmatter fields:

type CustomFields = {
  priority?: "low" | "medium" | "high";
  assignee?: string;
  estimate?: number;
};

const board = new Kanbamd<CustomFields>({
  root: "./board",
  columns: ["todo", "doing", "done"],
});

API

listColumns()

const columns: string[] = await board.listColumns();

listCards(options?)

const allCards = await board.listCards();
const todoCards = await board.listCards({ column: "todo" });

Returns Card<T>[] sorted by column then order.

getCard(locator)

const card = await board.getCard({ column: "todo", id: "fix-login" });

Card<T> shape:

| Field | Type | Description | |---|---|---| | id | string | Slug derived from title | | fileName | string | "<id>.md" | | column | string | Column the card belongs to | | frontmatter | CardFrontmatter<T> | Parsed YAML frontmatter | | body | string | Markdown body | | createdAt | Date | Filesystem birthtime | | updatedAt | Date | Filesystem mtime |

createCard(column, input)

const card = await board.createCard("todo", {
  title: "Fix login",
  tags: ["bug"],
  body: "OAuth callback fails.",
  frontmatter: {
    priority: "high",
    assignee: "alice",
  },
});

CreateCardInput<T>:

| Field | Type | Default | Description | |---|---|---|---| | title | string | required | Card title | | tags | string[] | [] | Tags | | body | string | "" | Markdown body | | frontmatter | NoReservedFrontmatter<T> | — | Custom fields |

Duplicate IDs get a numeric suffix: fix-login, fix-login-2, fix-login-3, etc.

updateCard(locator, input)

const updated = await board.updateCard(
  { column: "todo", id: "fix-login" },
  {
    title: "Fix OAuth redirect",
    tags: ["bug", "auth"],
    body: "Updated description.",
    frontmatter: { priority: "medium" },
  }
);

All fields in UpdateCardInput<T> are optional. Omitted fields keep their current value.

moveCard(locator, target)

await board.moveCard(
  { column: "todo", id: "fix-login" },
  { column: "doing" }
);

The source column's order is normalized (1, 2, 3, ...). The moved card is placed last in the target column. Throws DuplicateCardError if a card with the same ID already exists in the target column.

reorderCard(locator, index)

const reordered = await board.reorderCard(
  { column: "todo", id: "fix-login" },
  0   // 0-based new position
);

Returns the entire column's cards in their new order. Out-of-range indices are clamped.

deleteCard(locator)

await board.deleteCard({ column: "todo", id: "fix-login" });

The column's remaining cards are normalized.

searchCards(options)

const results = await board.searchCards({
  query: "oauth redirect",
  columns: ["todo", "doing"],
  tags: ["bug"],
  limit: 10,
});

Fuzzy search (Fuse.js, threshold: 0.35, ignoreLocation: true) across id, frontmatter.title, frontmatter.tags, and body. Tag filtering is AND-based.

Error classes

| Error | When | |---|---| | BoardRootNotFoundError | Root dir missing or not a directory | | ColumnNotFoundError | Column not in the defined list | | CardNotFoundError | Card file or ID not found | | DuplicateCardError | ID collision during move | | InvalidFrontmatterError | Invalid/reserved key in frontmatter | | InvalidStorageConfigurationError | Misconfigured storage options |

All extend KanbamdError.

CLI

The kanbamd binary ships with the package.

kanbamd init

Initialize a board. Creates column directories and a .kanbamd.json config.

kanbamd init
kanbamd init --no-fields                         # skip custom field prompts
kanbamd init --root ./board --columns todo,doing,done

By default, init prompts interactively to define custom frontmatter fields. Four field types are supported:

| Type | Input | Example | |---|---|---| | text | Free text | assignee, branch | | select | Single choice | priority (low/medium/high) | | multiselect | Checkboxes | labels (frontend, backend, devops) | | number | Integer with min/max | estimate, story-points |

Each can be marked required and have a default value.

kanbamd columns

kanbamd columns

Lists columns with card counts.

kanbamd list

kanbamd list
kanbamd list --column todo
kanbamd list -c todo

Cards shown as: <order>. [<column>] <title> #<id> #<tag1> #<tag2>

kanbamd add

Fully interactive. Prompts for: column (skipped if only one exists), title (required), body, tags (comma-separated), custom fields (if defined in config), and order (defaults to last).

kanbamd add

kanbamd view

kanbamd view fix-login                            # by ID
kanbamd view fix-login --column todo              # disambiguate
kanbamd view                                      # interactive picker

Displays: title, ID, column, order, tags, all custom fields, createdAt, updatedAt, and body.

kanbamd move

kanbamd move fix-login --to done                  # non-interactive
kanbamd move                                      # interactive picker

The target is auto-selected if only one other column exists.

kanbamd delete

kanbamd delete fix-login                          # by ID
kanbamd delete                                    # interactive picker

Always prompts for confirmation.

kanbamd search

kanbamd search "oauth bug"
kanbamd search "oauth" --tags bug,auth            # must have ALL tags
kanbamd search "oauth" --column todo,doing        # filter columns
kanbamd search "oauth" --limit 5                  # max results (default: 10)
kanbamd search "fix" -t bug -c todo,doing -l 20

Global options

These apply before any subcommand and override config:

kanbamd --root ./board --columns todo,doing,done list

If omitted, kanbamd walks up the directory tree looking for .kanbamd.json. Falls back to the current directory, auto-detecting columns from subdirectories.

Interactive fallback

Commands accepting an optional <id> (view, move, delete) show a select list when called without one. Ctrl+C exits cleanly.

Configuration

kanbamd init writes a .kanbamd.json file:

{
  "root": "./board",
  "columns": ["todo", "doing", "done"],
  "fields": [
    { "name": "priority", "type": "select", "options": ["low", "medium", "high"], "required": true },
    { "name": "assignee", "type": "text", "default": "unassigned" },
    { "name": "estimate", "type": "number", "min": 1, "max": 100 },
    { "name": "labels", "type": "multiselect", "options": ["frontend", "backend", "devops"] }
  ]
}

| Key | Type | Description | |---|---|---| | root | string | Path to board root, relative to this file | | columns | string[] | Ordered column names | | fields | FieldConfig[] | Custom field definitions (optional) |

Config is discovered by walking up from the working directory, so commands work from any subdirectory.