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

@frehilm/ordna-core

v0.1.4

Published

Git-native task management — pure data layer. Tasks are markdown files; the board is the directory.

Readme

@frehilm/ordna-core

The data layer for Ordna. Pure TypeScript — no I/O frameworks, no React, no UI. Importable from a CLI tool, a web server, an Electron main process, or an agent script.

This package is what @frehilm/ordna-cli and @frehilm/ordna-web are built on. If you only want to read and write tasks programmatically, install just this.

Install

pnpm add @frehilm/ordna-core
# or:    npm i @frehilm/ordna-core

Use

import {
  createContext,
  listTasks,
  createTask,
  moveTask,
  watchTasks,
  ARCHIVED_STATUS,
  type Task,
} from "@frehilm/ordna-core";

const ctx = createContext("/path/to/repo");

const tasks = await listTasks(ctx);
const created = await createTask({ title: "Implement payment flow", priority: "high" }, ctx);
await moveTask(created.id, "doing", ctx);

const stop = watchTasks(ctx, (event) => {
  // event.type: "added" | "changed" | "removed"
});
stop();

API

createContext(cwd?: string): StoreContext

listTasks(ctx, opts?: { status?, assignee?, tag? }): Promise<Task[]>
getTask(id, ctx): Promise<Task | null>
createTask(input: TaskCreateInput, ctx): Promise<Task>
updateTask(id, patch: TaskUpdateInput, ctx): Promise<Task>
moveTask(id, status, ctx): Promise<Task>     // depends_on gate on terminal status
deleteTask(id, ctx): Promise<void>

watchTasks(ctx, cb: (event: TaskEvent) => void): () => Promise<void>
commitTasks(ctx, message?): Promise<void>    // stages tasksDir + git commit

isKnownStatus(config, status): boolean
ARCHIVED_STATUS: "archived"

parseTask(raw, filePath): Task
parseTaskFile(filePath): Promise<Task>
serializeTask(task, mode: "ordna" | "backlog"): string
extractAcceptanceCriteria(sections): AcceptanceItem[]

Types: Task, Section, AcceptanceItem, Priority, SchemaMode, OrdnaConfig, StoreContext, TaskCreateInput, TaskUpdateInput, TaskEvent.

Task file format

Each task is one markdown file in tasks/. The filename is the ID.

---
id: T-001
title: Implement payment flow
status: todo
assignee: null
priority: high
tags: [payments]
depends_on: []
created_at: 2026-04-18
updated_at: 2026-04-18
---

## Goal
Ship a working payment flow.

## Acceptance Criteria
- [ ] Card works
- [ ] Apple Pay works

## Notes
Careful with PCI.

## Progress

Acceptance criteria are plain markdown checkboxes — the file is the source of truth, structured views are derived.

Dependencies

depends_on is enforced by moveTask: moving a task to the terminal status (last entry of statuses, done by default) while any dependency is unfinished throws. Other transitions are free.

Archiving

archived is a reserved built-in status — accepted by moveTask / updateTask regardless of whether it's listed in config.statuses. Use it to retire tasks without polluting the active board. The two UI packages filter archived tasks out of every other view by default.

Configuration

.ordna/config.yaml is optional. With no config, Ordna behaves exactly as documented above. Config only expands.

tasksDir: tasks            # where task files live
schema: ordna              # ordna | backlog
statuses: [todo, doing, done]
idPrefix: T                # custom prefix, e.g. BUG, EPIC
zeroPaddedIds: 3           # width of the numeric part (0 = no padding)
webPort: 7420              # consumed by @frehilm/ordna-web

The last entry of statuses is the terminal status for the dependency gate.

Backlog.md compatibility

Ordna reads Backlog.md repos out of the box. The parser normalizes both field sets:

| Ordna | Backlog.md | |---------------|---------------------| | tags | labels | | depends_on | dependencies | | created_at | createdDate | | updated_at | updatedDate | | assignee: "x" or null | assignee: ["x"] or [] |

To open a Backlog repo, point Ordna at its directory and set:

tasksDir: backlog
schema: backlog

In schema: backlog mode the writer uses Backlog-style filenames (task-1 - title.md) and field names. Tasks round-trip cleanly between tools.

Body sections in each schema

| Schema | Default body sections | |-----------|----------------------------------------------------------------------------------| | ordna | ## Goal / ## Acceptance Criteria / ## Notes / ## Progress | | backlog | ## Description / ## Acceptance Criteria / ## Implementation Plan / ## Implementation Notes / ## Final Summary |

Section headings are matched case-insensitively, with aliases (Goal/Description, Notes/Implementation Notes, Progress/Final Summary).

License

MIT — see LICENSE.