This package is retired. 0.7.0 is the final release and ships no functionality: every command prints a migration notice and exits non-zero. Older 0.6.x versions are unsupported and no longer work fully against the backend. Use GitHits instead.

Migrating

GitHits is the code context layer for AI coding agents. It covers what this CLI did — package metadata, vulnerabilities, dependencies, changelogs, docs, code navigation — and adds cross-OSS example search.

npx -y githits@latest init

The wizard detects your coding agents, signs you in, and writes the MCP and skill configuration. Uninstall the old CLI and drop any pkgseer entry from your agents' MCP configuration:

npm uninstall -g @pkgseer/cli

Command names carry over — pkgseer login, pkgseer search, pkgseer pkg …, pkgseer docs …, and pkgseer code … become githits …. Some surfaces moved or were renamed; see the GitHits docs for the current command reference and manual MCP setup.

What happens if you upgrade

CLI — any invocation prints the migration notice and exits 1.
MCP server — pkgseer mcp still starts and still advertises the tool names 0.6.16 exposed, but every tool call returns the migration notice as an error. This is deliberate: an agent that still has pkgseer configured reports the migration path instead of a server that failed to start.

Staying on 0.6.x will not work either

The backend has moved on. Query surfaces the older versions depend on are being removed — every search surface other than discovery search, for example — so 0.6.x returns errors or partial results, and it will keep degrading. Every published version is deprecated on npm and none will receive fixes.

Note that ^0.6.x ranges do not cross to 0.7.0, so a pinned install never picks up the migration notice on its own. Upgrade or uninstall.

This repository

Archived and read-only. The last functional implementation is on the v0.6.16 tag and the source remains in src/ for reference; only the entry point (src/cli.ts) was replaced. Issues and pull requests belong in githits-cli.