Skip to content

About

The list of plugins you can install in Termix.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

6 stars

Watchers

0 watching

Forks

Termix Logo

Termix Registry

The list of plugins you can install in Termix

Discord Donate OpenSSF Scorecard


Overview

This is the plugin registry for Termix, self-hosted, plugin-based server management. It has two lists:

  • official/index.json: the official Termix plugins. Each is built from its own Plugin-<Name> repo and released and signed by this repo. Termix reads it to show the plugins you can install from the Plugins tab.
  • community/index.json: plugins made by anyone and reviewed by a person before they are listed. Admins turn it on in Termix under Plugins, Registries.

Want to build your own plugin? Start from the plugin template. You can also host your own registry and add it to Termix by its URL. See host your own registry.


Submit a plugin

The community registry is open for submissions. Release your plugin with the template's Release workflow, then open a pull request that adds community/plugins/<id>.json. See CONTRIBUTING.md for the steps and what reviewers check.


Releasing official plugins

Maintainers run the Release Plugin workflow here with one plugin id or a comma list. Each plugin is built from its only dev-X.Y.Z branch with no secrets, then a person approves the release environment and the run signs it, merges the branch into main, tags and releases it. The signing key and the CI App key live only in this repo's environments, so plugin repos hold no secrets.

Before anything is signed, the release gate (release-gate.yml) runs on the same commit: zizmor on the workflows, osv-scanner on the lockfile, every GHSA-*.test.* regression test (none may be skipped), the authorization matrix, and a check for new high or critical CodeQL alerts. If one fails, nothing is published. Core's Release uses the same gate.

Once published, the release is built again from its tag on a separate machine with no keys. The index lists it only when that rebuild gives the same file, byte for byte.


Signing keys

Termix trusts only offline root keys, two per registry, kept in trust/<registry>/root.pub. They sign the certificates of the online keys the workflows use (trust/<registry>/certs.json, one year each) and the revocation lists (trust/<registry>/revocations.json). The Signing keys page covers how it works, the yearly renewal and what to do if a key leaks. The trust:new-key, trust:revoke, trust:sign and trust:check npm scripts do the work.


Sponsors

For a paid sponsor spot, email mail@termix.site.


Blacksmith     Cloudflare     Akamai     AWS     Rack Genius     Ginernet     Hetzner     Ember Swan

Support

Problems with the registry itself (a plugin missing from a list, a broken index) go in this repo's issues. A bug in a plugin goes in that plugin's own repo, and problems with Termix itself go in the Termix repo.

Add as much detail as you can, in English if possible.

For discussions and questions, join the Discord server.


License

Apache License 2.0. See LICENSE.

About

The list of plugins you can install in Termix.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

6 stars

Watchers

0 watching

Forks

Used by

Contributors

Languages