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

@linkeq/cli

v0.6.0

Published

LinkEQ CLI for agent and shell workflows

Downloads

77

Readme

LinkEQ CLI

Shell-native linkeq for agents and scripts. Same API as the SDK.

Install

npm i -g @linkeq/cli
# or
npx @linkeq/cli --help

Local / monorepo:

pnpm --filter @linkeq/cli build
pnpm --filter @linkeq/cli exec linkeq --help

Auth

Two paths. Steady state is a Bearer API key only (no device-code).

1. Env key (preferred)

export LINKEQ_API_KEY=lq_...
linkeq me --json

2. OTP bootstrap

Agent requests a code; a human pastes the 6-digit email code only.

linkeq auth otp [email protected] --json
linkeq auth verify [email protected] 123456 --json
# → { "api_key": "lq_...", ... }
export LINKEQ_API_KEY=lq_...

Global flags

| Flag | Env | Default | |------|-----|---------| | --json | — | pretty JSON; with flag, compact | | --base-url | LINKEQ_BASE_URL | https://api.linkeq.co | | --api-key | LINKEQ_API_KEY | — |

Local worker:

linkeq --base-url http://127.0.0.1:8787 me --json

Commands

Account

linkeq me

Sites

linkeq sites add example.com --method dns
linkeq sites add example.com --method file --include /blog --exclude /admin
linkeq sites list
linkeq sites get <site_id>
linkeq sites verify <site_id>
linkeq sites pages <site_id>
linkeq sites ingest <site_id> https://example.com/article
linkeq sites unindex <site_id> https://example.com/article
linkeq sites update <site_id> --status inactive
linkeq sites recrawl <site_id>
linkeq sites delete <site_id>
linkeq sites matches <site_id> --url https://example.com/article
linkeq sites internal <site_id> --urls https://example.com/a https://example.com/b
linkeq sites internal <site_id> --url https://example.com/article
linkeq sites internal <site_id> --url https://example.com/article --direction inbound
# --urls (preferred, max 50) → {ready, pages:[{source_url|target_url, ready, links}]}
# --url → ready + links[{source_url, target_url, suggested_anchor, relevance}]
# ready:false (HTTP 202) = embeddings not ready; empty links + ready:true = no gaps

Exchanges

linkeq exchanges list --status pending --role target
linkeq exchanges get <exchange_id>
linkeq exchanges create --requester <id> --target <id> \
  --requester-url https://yoursite.com/article --target-url https://partner.com/post
linkeq exchanges accept <exchange_id>
linkeq exchanges reject <exchange_id>
linkeq exchanges cancel <exchange_id>
linkeq exchanges placement <exchange_id>
linkeq exchanges verify <exchange_id> https://yoursite.com/page-with-link
linkeq exchanges health <exchange_id>

Agent example (--json) — internal links

export LINKEQ_API_KEY=lq_...
SITE=$(linkeq sites list --json | jq -r '.[0].id')
linkeq sites ingest "$SITE" https://example.com/article --json
linkeq sites internal "$SITE" --urls https://example.com/article https://example.com/other --json

Typical flow

  1. auth otp → human pastes code → auth verify → set LINKEQ_API_KEY
  2. sites add → place DNS/file proof → sites verify → wait until active
  3. sites ingest after publishing → sites internal --urls → place suggested anchors
  4. Optional: sites matches --url → exchanges create → partner accept → placement → verify