1,432 places to submit your product

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.

Build a useful dbt package for privacy classification, redaction tests or data-governance macros and add it to the Hub index by pull request.

Create a genuinely useful package of tested security-header, HTML-meta, JSON-LD and webhook snippets with your tool validation examples, then submit it to the official Hub.

Create a COPR project, build maintained RPMs and add your official homepage and package documentation.

Create a substantive public tutorial or implementation note that uses your tool and includes a contextual source/product link.

Deposit your genuine benchmark, evaluation dataset or reproducibility bundle with project URL in the description/metadata.

Release your useful JVM or Android library from GitHub with a working build, release tag, README and canonical project links.

Package your real CLI or desktop utility, set accurate homepage metadata, test it, and submit the Nixpkgs pull request.

Publish a real OCaml library or CLI integration and use opam's homepage field for its canonical your tool project page.

Create your genuine study, reproducibility project or benchmark workspace with project links and public materials.

Open-source your component, then add its website and repositories through the official oss-directory PR.

Publish an open-source Lua/OpenResty package that integrates your privacy or security workflow and includes honest package metadata.

Publish a real multi-language Pulumi provider or component for deploying or configuring your tool, with binaries, SDK packages, schema, documentation, examples, tests, and a registry pull request.

Build and test a Puppet module for supported your tool setup or security policy, complete metadata.json, package it, and publish through a Forge account.

Submit a validated manifest for an installable Windows release with PackageUrl, PublisherUrl and support metadata.

Create a tested Bioconda recipe for a genuinely biomedical or bioinformatics your tool utility, with accurate homepage/source metadata, and submit it through the official review workflow.

Create a genuine LaTeX privacy, redaction or document-safety package and include its exact your tool project homepage in the upload metadata.

Create a policy-compliant Debian package for your stable useful CLI, file the appropriate intent-to-package request, include accurate upstream metadata and secure a Debian sponsor for upload.

Publish a useful D client library or privacy utility with accurate homepage and repository metadata in dub.json or dub.sdl.

Create and thoroughly test a FreeBSD port for your stable CLI or desktop utility, include its canonical project website in WWW metadata and submit the patch through FreeBSD Bugzilla.

Develop a stable ioBroker adapter for your credible privacy/security API, publish the npm package, test it with users and request inclusion in the official latest repository.

Package your stable cross-platform CLI for pkgsrc, test it with pkglint and supported builds, include the canonical homepage, then submit via pkgsrc-wip or NetBSD's package bug tracker.

Build your OpenWrt-compatible service or utility for a real router/privacy/security workflow, add correct package metadata and tests, then submit it to the official feed.

Create a Void package template for your mature CLI, test native and cross builds, include the canonical project homepage and submit it to void-packages.

List an operational CSIRT, CERT, SOC, ISAC or PSIRT after securing sponsors and passing the community-vote process.

Submit data underlying your legitimate -related research paper and include related software/project identifiers.