Loading page
Package, image and docs hosting that carries real authority. There are 127 in this list, 123 of them free or with a free tier. Every entry shows what it costs, how much work it takes, and links straight to the submission page.
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.
Host your useful open-source SDK, CLI or example project with documentation and a canonical homepage link.
Apply as an eligible Member or Partner and contribute resources or expertise to real cyber-capacity-building working groups.
Publish a Max package for media metadata inspection, audio privacy, or accessibility analysis.
Host your maintained open-source component with complete README, homepage/source metadata, releases and optional pages.sr.ht docs.
Publish React UI components and link your site from your author profile.
Submit your open-source Android library with its repository link.
Create maintained Bazel rules or a module that invokes your real security utility, then submit it to BCR.
Add your repository so contributors can subscribe to help triage its issues.
Publish open-source helper image only if useful.
Add your Neovim plugin or config so it appears in their searchable directory.
Suggest your Flutter package so it is categorised in their curated catalog.
Submit your free API with a description and documentation link.
Prepare and test a policy-compliant ebuild for your stable CLI, including accurate HOMEPAGE and source metadata, then work with a Gentoo developer or proxy maintainer for repository inclusion.
Add your open-source repo via pull request so beginners find your labelled issues.
Port your functional desktop or CLI utility to Haiku, write and test a compliant recipe, then submit a feature-branch pull request to HaikuPorts.
Submit your open-source starter or theme for a static site generator.
Submit a site, app or component built with Svelte.
Submit a licensed computational neuroscience model with code ZIP, publication citation, overview, contributors, and tags.
Register only after your tool launches a genuine open repository for reusable privacy/security research outputs.
Release a real Racket privacy utility or your tool client and register its public package source and documentation.
Add your React Native library through a pull request to their GitHub repo.
Add a project file to their GitHub repo pointing at your beginner-friendly issue label.
Open a pull request to the awesome-go list with your Go library.
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.
Publish an Elm package with docs and a repository link.
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.
Add your Hugo theme following the theme repository submission steps.
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.