ADR-0010 records that the marketplace catalog holds package metadata only (names, authors, licenses, short descriptions, links, install instructions), like any package index, and needs no licensing review. The pending licensing row of the ADR index keeps only the copyright holder in LICENSE; the settled items (Apache-2.0 files in core, the notices and the LGPL terms, the catalog) are listed below the table. The README names the Apache-2.0 files of packages/core.
1.8 KiB
1.8 KiB
ADR-0010: The marketplace catalog stays in the repository
- Status: Accepted
- Date: 2026-11-04
Context
packages/marketplace/marketplace.db is the seed catalog of the Marketplace: a 14 MB SQLite
file with 8,129 packages (3,953 skills, 3,271 MCP servers, 905 plugins) gathered from 61 public
source repositories, plus 18 packs, tags, a full-text index and the security-scan settings. It
holds no user data. scripts/build-sidecar.mjs ships it next to service.js; on first start
the sidecar copies it into the data directory and later syncs new packages from the sources.
The plan (P1.6) suggested generating it at build time or publishing it as a release artifact, so that a data file does not grow the git history.
Decision
The catalog stays in the repository for v1. The project owner's representative chose this on 2026-11-04 over the two alternatives:
- generating it at build time would need network access during every build, and two builds could ship different catalogs;
- downloading it as a release artifact would leave the Marketplace empty without a network on first start.
Consequences
- The Marketplace works on first start without a network.
- Each catalog refresh adds about 14 MB to the history; refreshes stay rare. The public release is one commit (P2.6), so it starts with a single copy.
- The catalog carries package metadata of third-party packages: names, authors, declared licenses, short descriptions (66 characters on average, at most 391), version numbers, links and install instructions, as any package index does. It holds none of the packages' code or content; installing a package fetches it from its source. The project owner left the licensing question to us, and we settled it on 2026-11-04: the catalog needs no licensing review and no change.