The curated module registry for
nano-core — one
registry.json, Obsidian-style. A module appears here only after the
store maintainer reviewed that exact version (MELPA-style curation,
single-file resolution).
Clients (the nano-core CLI and TUI) fetch the raw registry URL,
cache it for 24 hours, and resolve module install <name> against
it — the same way package-install resolves MELPA.
- Exact-version pinning: an entry vouches for ONE version, reviewed
on
validated_at. - npm sources verify through the lockfile integrity hash; github
sources clone the
v<version>tag and can pin acommitSHA. - Anything not in this registry is an EXTERNAL install: nano-core shows a risk warning and records it as unreviewed.
- Removal from the registry is the kill switch;
module outdatedsurfaces removed entries to installers.
See SUBMISSIONS.md. PRs are validated by CI against registry.schema.json and reviewed by the maintainer.
| Module | Kind | Repository | What it does |
|---|---|---|---|
synapse | hybrid | ccs-devhub/nano-module-synapse | Base sensory module: scan guilds, roles, members, channels, vitals. |
mcp | extension | ccs-devhub/nano-module-mcp | AI bridge: an MCP server exposing the NanoResult API layer as tools. |
embed-styler | command | ccs-devhub/nano-module-embed-styler | Embed customization: themes, five templates, /embed send/preview. |
Every entry is pinned to a reviewed git tag and commit SHA. All
three also ship bundled inside the nano-core repository as the
reference copies; npm run module -- install <name> from a
nano-core checkout installs the published, pinned version (and
resolves the module’s own npm dependencies automatically on
nano-core >= 0.2.1).