Contribution workflow

Submit a plugin through a reviewed PR.

Community plugins enter the ServiceRadar ecosystem through pull requests that add the published package set to the Forgejo-backed registry. The portal reads the manifest, schema, checksum, signature, and WASM artifact links directly from that repository and keeps trust signals visible in the UI.

Step 1

Develop

Build the plugin with the Go or Rust SDK and compile it to WASM.

Step 2

Package

Prepare the manifest, config schema, checksum, signature, and WASM artifact set.

Step 3

Submit

Open a pull request that adds the published package files to the Forgejo-backed registry.

Step 4

Review

Maintainers review the package contents, trust fields, and install guidance.

Step 5

Publish

After merge, the plugin appears in the public registry.

Required package contents

Name, slug, author, version, and category
Language or SDK target such as Go or Rust
Manifest and config schema files users can download directly
Signed WASM artifact plus checksum and signature material
Source repository link and release notes when relevant
Install instructions and operational notes

Platform context

Authentication is expected to flow through Authentik with GitHub as the upstream source.
The site itself is delivered through Kubernetes and Argo CD-managed overlays.
Official and community entries must be clearly distinguishable in the registry UI.