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

@fureworks/scope

v0.3.6

Published

Personal ops CLI — focus on what matters

Readme

Scope

Scope tells you the 3 things that matter right now — and gives you permission to ignore everything else.

A personal ops CLI for builders who juggle multiple repos, PRs, meetings, and issues. Scope reads your existing workflow signals and surfaces what needs attention. No manual input. No new accounts. No cloud.

Install

npm install -g @fureworks/scope

Requires Node.js 18+.

Quick Start

scope onboard    # guided first-time setup
scope today      # what matters right now
scope review     # end-of-day summary

Or set up non-interactively (great for AI agents):

scope init
scope config repos add ~/projects/my-app ~/projects/api
scope config repos scan ~/work     # auto-discover git repos
scope config calendar enable
scope config projects add myproject --dir ~/projects/my-app

What It Does

Scope reads signals from tools you already use:

  • Git — uncommitted work, stale branches, recent activity
  • GitHub — open PRs, review requests, CI status, assigned issues
  • Google Calendar — meetings, free blocks (via gws CLI)

Then it scores and ranks everything using deterministic rules (no AI):

$ scope today

  Good morning. Here's what matters:

  NOW
  ───
  🔴 PR #8 on api-service (low context: no CI status)
     auth migration — review requested, 3 days old
     Why: Someone's waiting on your review. 3 days stale.

  TODAY
  ────
  🟡 fureworks/scope
     3 uncommitted files, last touched 6h ago
     Why: Uncommitted work for 6 hours. Commit or stash.

  IGNORED
  ───────
  ✗ PR #2 on docs — Fresh, no one's waiting
  ✗ Issue #12 on scope — Less than a week old, no priority label

  Nothing else needs you today.

Commands

| Command | What it does | |---------|-------------| | scope today | Morning priorities — what needs attention right now | | scope review | End-of-day summary — what got done, what's carrying over | | scope plan | Weekly view — calendar density, PR backlog, best build days | | scope status | Overview of all watched projects | | scope switch <project> | Context switch between projects | | scope context | Show current project state | | scope snooze <item> --until <date> | Hide an item until a date | | scope mute <item> | Permanently hide an item | | scope tune [key] [value] | Adjust scoring weights | | scope config repos\|calendar\|projects | Manage configuration | | scope init | Initialize Scope | | scope onboard | Interactive guided setup | | scope daemon start\|stop\|status | Background signal checks | | scope notifications | View recent alerts |

How Scoring Works

Each item gets a priority score based on measurable signals:

Score = (Time Pressure + Staleness + Blocking Potential + Effort Match) × Weight
  • Score ≥ 8 → 🔴 NOW — do these first (max 3 shown)
  • Score 4–7 → 🟡 TODAY — fit these in (max 5 shown)
  • Score < 4IGNORED — shown with reason, explicitly excluded

Adjust weights with scope tune:

scope tune staleness 1.5   # stale items rank higher
scope tune blocking 0.5    # reduce blocking urgency
scope tune --reset          # restore defaults

Time Awareness

scope today adjusts its tone based on when you run it:

  • Morning: "Good morning. Here's what matters."
  • Afternoon: "3/5 from this morning done. 2 remaining."
  • Evening: "Run scope review to wrap up."

Weekly Planning

$ scope plan

  THIS WEEK
  ─────────
  Mon  ████░░ 3 meetings, 2h free
  Tue  ██░░░░ 1 meeting, 5h free ← best deep work day
  Wed  █████░ 4 meetings, 1h free
  Thu  ███░░░ 2 meetings, 4h free
  Fri  █░░░░░ 0 meetings, 7h free

  BACKLOG
  ───────
  3 PRs older than 1 week
  2 issues approaching stale (>14 days)

  💡 Tuesday + Friday are your best build days this week.

Prerequisites

Scope reads from external tools. All are optional — missing integrations reduce output but never crash.

| Tool | What it provides | Install | |------|-----------------|---------| | gh (GitHub CLI) | PRs, issues, CI status | cli.github.com | | gws (Google Workspace CLI) | Calendar events, free blocks | npm i -g @googleworkspace/cli |

Best Practices

See WORKFLOW.md for habits that make Scope's output better — commit often, assign yourself, use labels, block focus time.

Philosophy

  • Zero manual input. Scope reads. It doesn't ask you to enter data.
  • Confident exclusion. The value isn't what's shown — it's what's hidden and why.
  • Degraded mode is fine. Only have git? Scope works. Add calendar? Better. Each integration is additive.
  • CLI-first, local-first. No accounts, no cloud, no tracking.
  • No AI (v1). Deterministic rules-based scoring. Transparent and predictable.

Data

Everything lives in ~/.scope/:

~/.scope/
├── config.toml          # configuration
├── contexts/            # saved project contexts
├── snapshots/           # daily snapshots (for review comparison)
├── muted.json           # snoozed/muted items
├── notifications.log    # notification history
└── daemon.pid           # background process

License

MIT — Fureworks