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

@nocoo/bogo

v0.5.0

Published

Command-line companion for bogo (https://bogo.hexly.ai) — generated from clip.yaml

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nocoonocoo

Keywords

bogocliclipcloudflare-access

Readme

@nocoo/bogo

Command-line companion to the bogo personal knowledge dashboard. The CLI is generated from the canonical clip.yaml so every endpoint in the worker is reachable as a subcommand.

Default endpoint: https://bogo.hexly.ai (the maintainer's deployment). Cloudflare Access gates the consent flow, so anyone running bogo login against the default URL must be on that Access policy — by design.

Self-hosting? Either set CLIP_BASE_URL=https://your-bogo.example.com to point this same CLI at your worker, or fork the repo and regenerate with your own alias / npm scope. See docs/features/03-self-hosting.md.

Install

# bun
bun add -g @nocoo/bogo

# npm
npm install -g @nocoo/bogo

Check the install:

bogo --version
bogo --help

Authenticate

bogo login

Opens your browser, walks through Cloudflare Access, asks you to click Authorize on a consent page, then writes a long-lived bearer to ~/.clip/bogo/credentials.json (mode 0600).

Running bogo login again automatically revokes any prior CLI token for the same account — one active token per identity.

Use

bogo me
bogo workspaces-list
bogo workspaces-create --name "Acme"
bogo persons-create <wid> --name "Alice" --managerId <root-id>
bogo documents-create <wid> --title "Plan" --personIds <p-uuid>
bogo tags-create <wid> --name "P0" --scope document

Path params (<wid>, <id>, …) are positional. Body / query fields are camelCase flags. Arrays go via comma-separated query (--personIds a,b). Booleans take an explicit value (--required true). Full command matrix and walkthroughs are in docs/features/02-cli.md.

Configuration

| Env var | Default | Purpose | | ---------------- | ------------------------------------ | ------------------------------------------------ | | CLIP_HOME | ~/.clip | Root of the credentials directory | | CLIP_BASE_URL | https://bogo.hexly.ai (from yaml) | API base URL for all requests (login + business). Set this to your own worker URL when self-hosting. |

CLIP_BASE_URL overrides both bogo login and every subsequent API call — one env var, full redirect, no rebuild. The hard-coded default from clip.yaml is the fallback when the env is unset.

Security

  • Tokens never leave your machine after issue; the worker stores sha256(token) only.
  • The CSRF / clickjacking protections live in the worker (two-stage consent + SameSite=Strict cookie + CSP); the CLI just rides them.
  • Revoke a leaked token immediately by running bogo login again, or ask the operator to UPDATE api_tokens SET revoked_at=… by prefix.

How it's built

bogo.hexly.ai  ←  clip.yaml (this repo)  →  clip generate  →  @nocoo/bogo

The package is published by running bun scripts/build.ts inside packages/cli/, which invokes clip to regenerate the CLI source, bundles it with bun build, and hands the resulting dist/ to npm. No source ships unbundled.

License

MIT