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

@studiometa/productive-cli

v0.10.9

Published

CLI tool for interacting with Productive.io API - optimized for AI agents and humans

Readme

@studiometa/productive-cli

npm version Downloads License: MIT

CLI tool for interacting with the Productive.io API. Optimized for both AI agents and human users.

Installation

npm install -g @studiometa/productive-cli

# Or use directly with npx
npx @studiometa/productive-cli --help

Configuration

Credentials can be provided in three ways (highest priority first):

  1. CLI arguments: --token, --org-id, --user-id
  2. Environment variables: PRODUCTIVE_API_TOKEN, PRODUCTIVE_ORG_ID, PRODUCTIVE_USER_ID
  3. Config file (persistent, with secure keychain storage):
productive config set apiToken YOUR_TOKEN
productive config set organizationId YOUR_ORG_ID
productive config set userId YOUR_USER_ID

productive config validate

API tokens are stored in the system keychain when available (macOS Keychain, Linux libsecret).

Commands

productive <command> [subcommand] [options]

| Command | Alias | Description | | ------------- | ----- | ------------------------------------------------------------- | | config | | Manage CLI configuration (set, get, validate, clear) | | projects | p | List and get projects | | time | t | List, get, create, update, delete time entries | | tasks | | List, get, create, update tasks | | people | | List and get people | | services | svc | List services | | companies | | List, get, create, update companies | | comments | | List, get, create, update comments | | timers | | List, get, start, stop timers | | deals | | List, get, create, update deals and budgets (--budget) | | bookings | | List, get, create, update bookings | | pages | | List, get, create, update, delete wiki/docs pages | | discussions | | List, get, create, update, delete, resolve, reopen | | activities | | List activity feed (audit log of create/update/delete events) | | reports | | Generate reports (time, project, budget, person) | | resolve | | Resolve human-friendly IDs (email, project number) | | api | | Make custom authenticated API requests | | cache | | Manage CLI cache (status, clear) | | completion | | Generate shell completions (bash, zsh, fish) |

Run productive <command> --help for detailed usage of each command.

Output Formats

All list/get commands support --format:

| Format | Flag | Description | | ------ | ---------------- | ------------------------------------ | | Human | --format human | Colored, readable output (default) | | JSON | --format json | Structured JSON for programmatic use | | CSV | --format csv | Comma-separated values | | Table | --format table | ASCII table |

productive projects list --format json
productive time list --format csv > time.csv

Smart ID Resolution

Use human-friendly identifiers instead of numeric IDs:

# Emails → person ID
productive time list --person "[email protected]"

# Project numbers → project ID
productive tasks list --project "PRJ-123"

# Explicit resolve
productive resolve "[email protected]"

Custom API Requests

For endpoints not covered by built-in commands:

# GET with filters and includes (recommended)
productive api /tasks --filter project_id=123 --filter status=1 --include project,assignee

# Mix with URL query params
productive api '/tasks?sort=-created_at' --filter project_id=123

# POST (auto-detected when fields are provided)
productive api /time_entries \
  --field person_id=12345 \
  --field service_id=67890 \
  --field date=2025-01-15 \
  --field time=480

# PATCH
productive api /time_entries/123456 --method PATCH --field time=240

# Paginate all results
productive api /time_entries --paginate --filter person_id=12345

Global Options

| Option | Alias | Description | | ----------------- | ----- | ---------------------------------------------- | | --format <fmt> | -f | Output format: json, human, csv, table | | --page <num> | -p | Page number | | --size <num> | -s | Items per page (default: 100) | | --sort <field> | | Sort field (prefix with - for descending) | | --no-color | | Disable colored output | | --token <token> | | API token override | | --org-id <id> | | Organization ID override | | --user-id <id> | | User ID override |

AI Agent Integration

The CLI is designed for programmatic use by AI agents. See the AI agent integration guide in the repository root for detailed workflows, response schemas, and examples.

Key features:

  • Structured JSON output with --format json
  • Consistent error format with status codes
  • Standard exit codes (0 = success, 1 = error)
  • Non-interactive, fully scriptable

Library Usage

The CLI can also be used as a Node.js library:

import { ProductiveApi, setConfig } from '@studiometa/productive-api';

setConfig('apiToken', 'your-token');
setConfig('organizationId', 'your-org-id');

const api = new ProductiveApi();
const projects = await api.getProjects({ page: 1, perPage: 50 });

License

MIT © Studio Meta