Syncing is not real-time
The Hub runs automatic discovery every 6 hours. If your plugin was just published to npm, it needs to wait for the next discovery cycle to appear in the catalog.
Manually accelerate syncing
Submit the package name directly on the plugins page and the Hub will prioritize it. Signed-in publishers can also use the "Sync Now" action in the Dashboard for real-time results.
Common rejection reasons
Missing dsh.bundle or dsh.profile field — the Hub only accepts packages with a valid DSH manifest.
Version is not exact SemVer — check for ^ or ~ prefixes.
Cordis patch file missing or malformed — ensure the patch path is correct and the YAML syntax is valid.
Package size exceeds the limit — the Hub enforces a size cap.
npm package doesn't exist or was removed — confirm the package is still accessible on npm.
GitHub source-only listings
Even without an npm package, a GitHub repository tagged with the dsh-plugin or deepseek-harness topic appears in the catalog as a source-only listing. Users can see the repository info but can't install it directly.
Once you publish the npm package, the source-only entry is automatically upgraded to a full plugin record on the next sync.