market vs marketplace vs hub: plugin terms compared

market, marketplace, hub, and store are not four synonyms. They point to a built-in interface, a third-party platform, a community Hub, and slang; confusing them leads to the wrong page and the wrong source.

What each term points to

Start with a comparison table.

market is a feature name. It refers to the plugin market screen and appears in many searches (source).

marketplace is more like a platform. It emphasizes catalog and distribution and usually belongs to a third party.

hub is an aggregation entry. DSH Plugin Hub is the most common usage, referring to the built-in community market (source).

store is slang. The community uses it for the market, without a separate definition; read the context as market.

market: the built-in interface

The core of market is the interface, not the repository.

1. The entry is under Settings, Plugin Market.
2. It provides categories, search, sorting, and card details.
3. Installation writes to a local profile and does not change the source.
4. Updates and uninstalls happen on the same screen.
5. Its data comes from an index, not live crawling.

market is not the source, and people searching it usually want the entry. The market shows entries; installation uses npm or GitHub. The source label matters more than the market name, and "where to open it and how to use it" answers the search better than architecture.

marketplace: third-party inclusion

marketplace more often means a third-party platform whose inclusion and verification belong to its project.

1. It may be installed as a plugin, such as dshmarket.
2. Inclusion rules differ from the Hub; information may overlap or be missing.
3. Installation still uses the real source; the market is only discovery.
4. Version and verification may lag, so check the source.
5. It should not be the only trust source.

Its value is an alternative discovery path; do not treat inclusion as an allowlist. The built-in market covers most needs. Inclusion is not security; source, owner, and version are the deciding factors.

hub: aggregation entry

hub emphasizes aggregating many things; DSH Plugin Hub is the clearest example.

1. It puts plugins, categories, sources, and verification in one entry.
2. It is both an interface and a project name; search may land on a page or repository.
3. It is not affiliated with the vendor; it is a community project.
4. Its inclusion follows an index and sync cycle, not real time.
5. It can serve as the main discovery and installation entry.

hub and market may overlap in the UI, but people searching hub usually want the project or page. The built-in market is the Hub's interface; hub emphasizes project and entry, market emphasizes function. "What it is and how it relates to the vendor" answers the search better.

store: slang

store has no separate definition; it is usually a spoken form of market.

1. The community uses "plugin store" for the built-in market.
2. A few contexts mean a third-party platform.
3. It carries no consistent inclusion or verification meaning.
4. Read the page subject instead of the word.

Slang is poor for precise judgment, though an article may mention it as a synonym. It has no stable extension and produces noisier search results. Do not treat store as a separate concept, or you create more confusion.

Search landing: which term to use

Choose by purpose for a more precise landing.

Chinese search favors the generic plugin market; English search differs by target. Find entry use market, find platform use marketplace, find project use hub; each covers a subset.

A title can cover two or three terms, then explain each in the body. That covers search without merging concepts.

Three common misreads

Three misreads dominate these terms.

1. "The four are one thing." They point to different objects and maintainers.
2. "Marketplace inclusion means safe." Inclusion is discovery, not verification.
3. "Hub is official." DSH Plugin Hub is a community project, not affiliated with the vendor.

The cost is misplaced trust. Treating third-party as official brings risk; treating a market as a source hides the real update address.

The standard is always the source. Package name, owner, and version aligned beat any market name.

Next steps

Identify the object, choose the term, verify the source. For the Hub workflow, read How to install from DSH Plugin Hub. For third-party markets, read What dshmarket is. For the market concept, read What dsh plugin market means.

Sources: DSH Plugin Hub plugin page, DSH Plugin Hub 2.2.5 screenshot index, dsh CLI README