Portfolio Configuration

Select the registries and packages included in reporting. All data remains local to this installation.

Tracked Portfolio

Add packages by registry. One entry per line within each array.

Supported Registries

npm @scope/pkg

PyPI package-name

VS Code pub.extension

NuGet Ns.Package

Docker Hub user/image

Advanced

Engine

registry-stats

Schema

1.0

Last Snapshot

None

Coverage

0 / 5

Branding

Product: Registry Pulse

Organization: MCP Tool Shop

🔄

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.

Install

npm i -g @mcptoolshop/registry-sync

Audit

registry-sync audit --org my-org

Plan & Apply

registry-sync plan --org my-org

What it detects

✓ Current — published version matches repo

⚠ Behind — repo version ahead of published

✗ Missing — not yet published to registry

○ Orphan — published but no matching repo

npm GitHub Docs

portfolio → registry-sync (publish) → registry-stats (monitor) → snapshot → dashboard