Portfolio Configuration
Select the registries and packages included in reporting. The portfolio file stays on this machine. Refresh reads public registry data and does not upload it.
Add packages by registry. One entry per line within each array. This file is the arrays npm, pypi, vscode, nuget, docker, and github, plus an optional npmMaintainer string. It is not registry-stats.config.json. A non-empty npmMaintainer is what the site fetch passes to stats.mine, which adds discovered names that are not already in the npm array. If discovery throws, the fetch warns and keeps the explicit npm list.
Supported Registries
Advanced
Registry Sync
Write-side companion — keep every registry in sync
registry-stats monitors downloads.registry-sync manages publishing. Together they close the loop: audit your org against npmjs and GHCR, detect version drift, find orphaned packages, and generate action plans — like Terraform for package registries.
npm i -g @mcptoolshop/registry-syncregistry-sync audit --org my-orgregistry-sync plan --org my-orgWhat it detects
portfolio → registry-sync (publish) → registry-stats (monitor) → snapshot → dashboard