1,432 places to submit your product

Create a valid Helm, OPA, Tekton or supported repository for your deployment and add it through the control panel.

Publish your genuine Rust client, CLI, parser, or privacy library and set homepage, repository, README, license, and documentation metadata.

Publish your standards-based JavaScript or TypeScript SDK with generated docs, readme and project links.

Create a useful Julia client or data utility, register it in Julia General and provide complete package docs with your source link.

Package your real MCP server, verify its namespace, create server.json and publish it with mcp-publisher.

Publish your open Privacy Framework mapping, template, tutorial, or implementation tool and submit it for repository review.

Build a genuine Kubernetes Operator for your self-hosted service, test its bundle and submit it through Community Operators.

Publish your real PHP SDK or integration from a public repository and set the canonical homepage in composer.json.

Publish your real Python SDK, CLI, or integration package and set Homepage, Documentation, Source, and Issues URLs in package metadata.

Publish a secure, documented container for your open service and add its official site in the repository description or README where supported.

Publish and maintain your genuine Ruby client, CLI, or integration gem with accurate homepage, source, documentation, and changelog metadata.

Create and maintain a PKGBUILD for your installable Linux release with the upstream URL and correct source checksums.

Build your useful privacy or security Caddy module, publish the Go package, then register it for module docs and custom builds.

Package your genuine Windows desktop or CLI release and set project, documentation and package-source URLs.

Ship your real CLI or desktop utility as a tested package with homepage, project and support metadata.

Publish your tested public orb for privacy, secret, or document-safety checks with a homepage URL and usage examples.

Publish a useful C/C++ SDK or client for your API and contribute its tested recipe to ConanCenter.

Submit a tested recipe for your real package with upstream homepage, source archive, license and tests.

Submit a useful R package with URL and BugReports metadata pointing to its official project and documentation pages.

Publish your maintained CLI or server image with source, documentation, descriptions and canonical homepage links.

Create a functional Drupal integration or reusable module and publish a maintained project page with documentation and official links.

Tag and publish a public Go module with module docs and repository metadata so pkg.go.dev indexes it.

Publish your useful package to a supported registry with accurate source and homepage metadata so Open Source Insights can index it.

Publish a maintained Elixir client or utility with package links, description, license and documentation.

Submit an open-source CLI formula or a qualifying macOS app cask with your canonical homepage.

Create and test a Portfile for your open-source CLI or desktop app, including its canonical homepage.

Release a useful Java or Kotlin SDK and include the project homepage, source control, license and developer metadata in the POM.

Create a useful Emacs client for your public API, host its source openly and submit a MELPA recipe pull request.

Add and test a Nix expression for your genuine release with description, homepage, license and maintainer metadata.

Publish @your tool/embed or utility package with homepage.

Publish your small local-first classifier for privacy, secret detection, or defensive content analysis.

Submit your maintained open-source project through Submit a Project.

Run Scorecard on your public component, enable published results, remediate checks, and link the public viewer from repository documentation.

Create a public OBS project and package that builds your tool for supported Linux distributions with upstream links.

Publish your reproducible testing, privacy-analysis or accessibility-evaluation method and cite relevant project resources.

Package your legitimate Ruby client or utility and add homepage and source metadata before pushing the gem.

Add a public Swift package with Package.swift, semantic-version tags, documentation and your homepage link.

Build a defensive Zeek script or plugin for privacy-safe log inspection, include zkg metadata and tests, then register it in the default Zeek package source.

Package your stable CLI or self-hosted helper as a tested APKBUILD, add it under Alpine testing and submit an aports merge request with accurate project metadata.

Submit your original -related technical paper and cite your tool only where it is genuinely the software or study subject.