Vibeleaderboard
← Back to Tools
Index / tool

Logseq Marketplace

https://github.com/logseq/marketplace
Visit logseq.github.io
Category
Productivity
Rank
No. 781Tools index
Pricing
Open Source
Type
TOOL
Builder
logseq
GitHub
358 stars
Date

About

Centralized package manager and registry for Logseq community plugins.

What it does

It turns one manifest per plugin into a browsable catalogue. Maintainers rebuild aggregated plugin data, fetch repository and release metadata from GitHub, and generate a searchable HTML table with compatibility, theme, author, repository, and README details.

Why it's ranked here

The project earns attention because its contribution contract is concrete and its output is inspectable. Release archives, descriptive documentation, visual proof, manifests, block rules, compatibility flags, and failure records create a practical publication pipeline. The implementation is useful, though operationally rough in places.

What's good

Plugin entries carry explicit flags for browser support, graph compatibility, themes, and elevated same-origin behavior. Blocked repositories support owner-wide rules with individual exceptions. Statistics collection preserves failed jobs separately, throttles requests, skips recently fetched data, and excludes draft releases from release summaries.

Tradeoffs

Publishing requires a fork, manifest, GitHub pull request, tagged release, and attached archive. Catalogue generation depends heavily on GitHub APIs and tokens, with explicit rate-limit handling. The elevated same-origin option can affect stability, triggers stricter review, and may not remain permitted.

How to use it well

It suits Logseq plugin authors preparing public releases and maintainers curating discoverable, compatibility-labeled entries. Keep the plugin SDK current, automate release archives, document usage, and include visual proof. Use the linked samples and API documentation for plugin development itself, which this repository does not provide.

Technical notes+

scripts/build.mjs reads manifests under packages, filters entries through blocked.json, derives addedAt from Git history, and writes plugins.json; its --stat action fetches GitHub repository and release data into stats.json while recording failures in errors.json. It prints the first eight characters of LSP_MK_TOKEN, an avoidable credential disclosure, and defaults proxy configuration to localhost. scripts/check_compatible.mjs downloads and extracts source archives from main or master branches and can update compatibility flags. catalog/scripts/fetch-plugins-data.js, catalog/scripts/update-catalog-index.js, and catalog/scripts/generate-plugins-table-html.js form the catalogue pipeline. The generator interpolates plugin metadata into HTML without visible escaping in the supplied code, so manifest content should be treated as an injection boundary. bb.edn adds listing, statistics, filtering, and manifest validation tasks.

Observed

License
MIT License
Primary implementation
JavaScript ES modules, with additional Babashka tasks written in Clojure
Publishing surface
Plugin authors submit a manifest through a GitHub pull request and provide a tagged release with an attached ZIP archive
Interfaces
Public web catalogue plus command-line maintenance and catalogue-generation scripts
Platform metadata
Manifests can declare browser support, file or database graph compatibility, theme status, and same-origin behavior
Validation
Babashka validation requires every aggregated plugin to provide title, description, author, and repository fields
Failure tracking
Statistics jobs persist unsuccessful package processing separately from collected statistics

Read from README.md, package.json, scripts/build.mjs, scripts/check_compatible.mjs, catalog/scripts/fetch-plugins-data.js, catalog/scripts/update-catalog-index.js, catalog/scripts/generate-plugins-table-html.js, bb.edn, LICENSE, stats.json, errors.json, blocked.json, plugins.json, popular.json.

What it can do

  • Browse available Logseq plugins

    User search query or category filter → List of matching plugins with descriptions and metadata

  • Install Logseq plugins

    Selected plugin from marketplace → Plugin installed and activated in Logseq application

  • Update existing plugins

    Installed plugins with available updates → Updated plugin versions in Logseq

  • Uninstall plugins

    Currently installed plugin selection → Plugin removed from Logseq application

  • Publish plugins to marketplace

    Plugin package and metadata from developer → Plugin listed in public marketplace registry

  • Manage plugin dependencies

    Plugin installation request with dependencies → All required dependencies automatically installed

Tags

logseqpluginsmarketplacenotes

Tech Stack

Node.js

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.