npm / npm/cli

New package missing from registry search index for 3+ days

Open
#9,991 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

Title: New package missing from registry search index for 3+ days

Package: picgo-plugin-upyun-sync-delete (unscoped, public)

Published: v1.0.0 on 2026-09-13T08:17Z, v1.0.1 on 2026-09-13T10:29Z (npm account: young143)

Problem

The package does not appear in the registry search endpoint (https://registry.npmjs.com/-/v1/search?text=picgo-plugin-upyun-sync-delete), which returns unrelated results. It has been missing for 3+ days — far beyond the usual indexing delay.

What we verified
  • Packument is fine on the primary registry: https://registry.npmjs.org/picgo-plugin-upyun-sync-delete returns both versions (1.0.0, 1.0.1), correct dist-tags, keywords, description, readme.
  • CDN download stats are recorded: https://api.npmjs.org/downloads/range/2026-09-13:2026-09-16/picgo-plugin-upyun-sync-delete shows 289 downloads on 09-13, 18 on 09-14 (mirror syncs), so the package clearly exists in the CDN/logs.
  • Packages published around the same time (e.g. adp-web-components, acp-kernel, expo-android-glass-view) appear in the search index within minutes, so the indexer was running normally.
  • A re-publish (v1.0.1) did not help either.
  • Search is important for this package because PicGo (https://github.com/Molunerfinn/PicGo), the app it targets, uses /-/v1/search for its in-app plugin market, so users cannot find or install it via the GUI.
Request

Could you check whether this package got stuck/missed in the search indexing pipeline, and re-index it?

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the package packument at registry.npmjs.org with the failing /-/v1/search response and review the search indexing pipeline for missed packages. Verify whether picgo-plugin-upyun-sync-delete is present in the index and identify why both published versions were skipped. Done means the package appears in registry search for its exact name and can be found by PicGo.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
backend-api-design, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.