metamask / snaps-registry

A registry containing metadata about verified and blocked Snaps.

snaps-registry

A registry containing metadata about verified and blocked Snaps.

Installation

yarn add @metamask/snaps-registry

or

npm install @metamask/snaps-registry

Contributing

Setup

• Install Node.js version 14
  • If you are using nvm (recommended) running nvm use will automatically choose the right node version for you.
• Install Yarn v3
• Run yarn install to install dependencies and run any required post-install scripts

Testing and Linting

Run yarn test to run the tests once. To run tests on file changes, run yarn test:watch.

Run yarn lint to run the linter, or run yarn lint:fix to run the linter and fix any automatically fixable issues.

Release & Publishing

The project follows the same release process as the other libraries in the MetaMask organization. The GitHub Actions action-create-release-pr and action-publish-release are used to automate the release process; see those repositories for more information about how they work.

1. Choose a release version.

   • The release version should be chosen according to SemVer. Analyze the changes to see whether they include any breaking changes, new features, or deprecations, then choose the appropriate SemVer version. See the SemVer specification for more information.

2. If this release is backporting changes onto a previous release, then ensure there is a major version branch for that version (e.g. 1.x for a v1 backport release).

   • The major version branch should be set to the most recent release with that major version. For example, when backporting a v1.0.2 release, you'd want to ensure there was a 1.x branch that was set to the v1.0.1 tag.

3. Trigger the workflow_dispatch event manually for the Create Release Pull Request action to create the release PR.

   • For a backport release, the base branch should be the major version branch that you ensured existed in step 2. For a normal release, the base branch should be the main branch for that repository (which should be the default value).
   • This should trigger the action-create-release-pr workflow to create the release PR.

4. Update the changelog to move each change entry into the appropriate change category (See here for the full list of change categories, and the correct ordering), and edit them to be more easily understood by users of the package.

   • Generally any changes that don't affect consumers of the package (e.g. lockfile changes or development environment changes) are omitted. Exceptions may be made for changes that might be of interest despite not having an effect upon the published package (e.g. major test improvements, security improvements, improved documentation, etc.).
   • Try to explain each change in terms that users of the package would understand (e.g. avoid referencing internal variables/concepts).
   • Consolidate related changes into one change entry if it makes it easier to explain.
   • Run yarn auto-changelog validate --rc to check that the changelog is correctly formatted.

5. Review and QA the release.

   • If changes are made to the base branch, the release branch will need to be updated with these changes and review/QA will need to restart again. As such, it's probably best to avoid merging other PRs into the base branch while review is underway.

6. Squash & Merge the release.

   • This should trigger the action-publish-release workflow to tag the final release commit and publish the release on GitHub.

7. Publish the release on npm.

   • Wait for the publish-release GitHub Action workflow to finish. This should trigger a second job (publish-npm), which will wait for a run approval by the npm publishers team.
   • Approve the publish-npm job (or ask somebody on the npm publishers team to approve it for you).
   • Once the publish-npm job has finished, check npm to verify that it has been published.

snaps-registry's Issues

Harden the allow list

The snaps-registry contains:

• TypeScript types
• Blocklist data
• Allowlist data
  • Snap metadata like user readable names

At least the allowlist data has to be hardened, only the @metamask/npm-publishers team should be able to deploy new versions of the allowlist.

We need to figure out a way how to secure those deployments and then implement.

One possible venue is having a separate production branch, similar how the gh-pages branch is hardened.

Additional info: https://app.zenhub.com/workspaces/snaps-615b3a7c08d2b20015eb6c4e/issues/gh/metamask/snaps-registry/14

Secure allow-list against Man-In-The-Middle attacks

The allow list will be downloaded through some kind of proxy or CDN because GitHub doesn't allow using their repositories are production sites.

We need to ensure that the proxy can't modify the integrity of allow-list in any way.

One possibility would be to use the signing key of the extension to sign the registry as well.

Outcome

• Research and decide on the solution to the MITM
• Implement the solution in the snap-registry and the extension

Allow Snap Registry to have allow listed snaps based on semver ranges

TK

Update the CI to verify the snap-registry published version

When publishing new snap-registry allowlist, the CI should check:

1. The structure of the allow list
2. That the private key signature of the published version is valid

It should block the release if those two are not satisfied.