zexadev/dsh-tether has been in the catalog since first_seen_at: 2026-08-21T03:50:27.358Z, and repo metadata syncs fine (last_synced_at and pushed_at both track my latest push, description updates propagate). But the install probe has never produced a result:
"install": {
"cmd": null, "source": "", "kind": null,
"pkg_name": null, "npm_published": false, "probed_at": null
}is_plugin is also still null.
Because of that the entry is absent from /market/v1/plugins (the DSH Desktop catalog source), so it can't be installed from the Desktop market.
Why this looks like it isn't just queue lag: sampling /v1/plugins, entries first seen on 2026-08-25 and 2026-08-26 are already probed (probed_at set, kind derived). Mine, first seen four days earlier, is not. Reading scripts/probe-install.mjs, the selection is is_present = 1 AND is_offtopic = 0 AND (install_probed_at IS NULL OR ...) with --min-stars defaulting to 0 and no row cap — so an unprobed row should be picked up by the daily run.
The package side should satisfy the desktop preview rules:
- npm:
dsh-plugin-tether, currently 0.1.8, exact stable versions only
repository → git+https://github.com/zexadev/dsh-tether.git (backlink present since 0.1.7; it was genuinely missing before that, which I fixed)- root
package.json declares dsh.bundle.patch: ./cordis.patch.yml, and that file exists on the default branch
- no
preinstall / install / postinstall / prepare scripts (scripts is absent entirely)
- MIT, public repo,
dsh-plugin topic set
Could you run a targeted re-probe (--only zexadev/dsh-tether)? If it runs and legitimately fails a check, I'd much rather know which one — happy to fix it on my side.
For reference, the same package is listed and installable on other catalogs, so the npm identity resolves fine from outside.
zexadev/dsh-tetherhas been in the catalog sincefirst_seen_at: 2026-08-21T03:50:27.358Z, and repo metadata syncs fine (last_synced_atandpushed_atboth track my latest push, description updates propagate). But the install probe has never produced a result:is_pluginis also stillnull.Because of that the entry is absent from
/market/v1/plugins(the DSH Desktop catalog source), so it can't be installed from the Desktop market.Why this looks like it isn't just queue lag: sampling
/v1/plugins, entries first seen on 2026-08-25 and 2026-08-26 are already probed (probed_atset,kindderived). Mine, first seen four days earlier, is not. Readingscripts/probe-install.mjs, the selection isis_present = 1 AND is_offtopic = 0 AND (install_probed_at IS NULL OR ...)with--min-starsdefaulting to 0 and no row cap — so an unprobed row should be picked up by the daily run.The package side should satisfy the desktop preview rules:
dsh-plugin-tether, currently0.1.8, exact stable versions onlyrepository→git+https://github.com/zexadev/dsh-tether.git(backlink present since 0.1.7; it was genuinely missing before that, which I fixed)package.jsondeclaresdsh.bundle.patch: ./cordis.patch.yml, and that file exists on the default branchpreinstall/install/postinstall/preparescripts (scriptsis absent entirely)dsh-plugintopic setCould you run a targeted re-probe (
--only zexadev/dsh-tether)? If it runs and legitimately fails a check, I'd much rather know which one — happy to fix it on my side.For reference, the same package is listed and installable on other catalogs, so the npm identity resolves fine from outside.