Skip to content
Back to search

reasonix-registry

Signed content registry for Reasonix Studio: community skills, themes, MCP servers and plugins, reviewed by PR and published as a minisign-signed index.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/1012905--reasonix-registry/badge.svg)](/listings/1012905--reasonix-registry)

HTML

<a href="/listings/1012905--reasonix-registry"><img src="/api/listings/1012905--reasonix-registry/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 115 lines
  1. # Reasonix Registry
  2. Curated skills, themes, MCP server manifests and plugins for Reasonix Studio.
  3. Content enters by pull request, CI validates it, and every merge to `main`
  4. publishes a minisign-signed `index.json`. This repository replaces the retired
  5. account-gated market: there is no account, no upload endpoint, and no server to
  6. run.
  7. ```
  8. skills/<id>/SKILL.md skill body with YAML frontmatter
  9. skills/<id>/skill.json registry metadata
  10. themes/<id>/theme.json theme pack, read by the kernel as-is
  11. themes/<id>/assets/ background.<ext> / preview.<ext>
  12. mcp/<id>.json one MCP server manifest
  13. plugins/<id>/plugin.json registry descriptor
  14. plugins/<id>/package/ the kernel package (reasonix-plugin.json + files)
  15. index.json generated catalogue, committed for review
  16. revoked.json append-only revocation records
  17. schemas/ JSON Schema for every manifest and the index
  18. scripts/build-index.mjs builds and checks index.json
  19. scripts/validate-schemas.mjs dependency-free schema gate
  20. registry.pub minisign public key, same key as app updates
  21. ```
  22. ## What the app reads
  23. The distributed artefacts are the assets of the newest release:
  24. ```
  25. https://github.com/<owner>/reasonix-registry/releases/latest/download/index.json
  26. https://github.com/<owner>/reasonix-registry/releases/latest/download/index.json.minisig
  27. ```
  28. The client, in order:
  29. 1. Fetch both files and keep the index bytes exactly as received.
  30. 2. Verify `index.json.minisig` over those bytes with the embedded minisign key
  31. (`internal/platform/update.Verify` in the kernel). A failure means discard the
  32. index and keep the last good one.
  33. 3. Resolve every path against
  34. `https://raw.githubusercontent.com/<owner>/reasonix-registry/main/`. Paths are
  35. repository-relative on purpose, so a fork's index stays valid; `url` locates
  36. the entry, `files` lists what it contains.
  37. 4. Fetch each file, hash it, and require its digest and size to match the entry's
  38. `files` row before writing anything. Then rebuild the listing described below
  39. and compare it with the entry's `sha256`. A mismatch means the index on `main`
  40. moved after the release, or the content was tampered with. Refetching the
  41. index resolves the first case.
  42. 5. Offer an entry only when the running app version is at least `minVersion` and
  43. its platform and frontend appear in `compat`, and only when `revoked` is
  44. `false`.
  45. `index.json` in `main` is the review artefact and the input to signing; the
  46. release asset is the distribution channel. Publish verifies the committed index
  47. is current before signing it, so the bytes a reviewer approved are the bytes the
  48. key covers.
  49. ## Entry digest
  50. `sha256` in the index covers the whole entry directory:
  51. 1. Take every committed file below the entry path. Skip `.gitkeep`, `.DS_Store`
  52. and `Thumbs.db`.
  53. 2. Sort the files by repository-relative path, forward slashes, byte order.
  54. 3. For each file, hash its bytes with SHA-256 and render one line:
  55. `<sha256 of the file><TAB><path><LF>`.
  56. 4. Hash that listing as UTF-8 with SHA-256. That hex string is the entry's
  57. `sha256`.
  58. The listing is the contract, so the index carries it as `files` (path, SHA-256 and
  59. size per file) — a static host cannot list a directory, and without the list a
  60. client could not verify what it downloaded. The aggregate digest binds the list to
  61. the entry; both are checked.
  62. ## Signing key
  63. The registry is signed with the same minisign key as Reasonix app updates, ID
  64. `441E92EFE08CA57F`; the public half is committed as `registry.pub` and embedded
  65. in the kernel. The private half exists only as the `MINISIGN_PRIVATE_KEY` and
  66. `MINISIGN_PASSWORD` secrets of this repository. Rotating the key means changing
  67. the kernel constant, `registry.pub`, and both secrets in one release.
  68. ## Publishing
  69. On every push to `main` that touches content, `publish.yml` re-checks the committed
  70. index, signs it, and creates a release tagged `registry-<timestamp>` with
  71. `index.json` and `index.json.minisig` attached. Release assets rather than a bot
  72. commit, because:
  73. - the signed snapshot is immutable and addressable by tag, while a second commit
  74. on `main` would need a branch-protection exception for a machine account;
  75. - `releases/latest/download/...` is one stable URL for the client;
  76. - a revocation or a new version is a new release, never a rewrite of the old one.
  77. The cost is one duplicated `index.json` (git and release). The git copy is the
  78. review input; only the release copy is signed and served.
  79. ## Adding content
  80. See [CONTRIBUTING.md](CONTRIBUTING.md). The short loop:
  81. ```bash
  82. node scripts/build-index.mjs # rewrite index.json
  83. node scripts/build-index.mjs --check # what CI fails on
  84. node scripts/build-index.mjs --caps # per-entry byte and file counts
  85. node scripts/validate-schemas.mjs # schemas/ against every manifest
  86. ```
  87. Node 24, no dependencies, no install step.
  88. `scripts/validate-schemas.mjs` implements the JSON Schema subset these schemas
  89. use: `type`, `required`, `properties`, `additionalProperties`, `items`, `enum`,
  90. `const`, `pattern`, string length, numeric bounds and array bounds. A schema that
  91. needs another keyword extends the validator in the same pull request; there is no
  92. npm install and no lockfile to trust.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.