Loading page
Package, image and docs hosting that carries real authority. There are 109 in this list, 105 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 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.
Build and upload a real conda package with homepage, documentation, source and license metadata.
Submit only after public privacy policy and client-side privacy proof.
Create a tested Chef cookbook for supported your tool deployment or hardening, add complete metadata and source, then share it to Supermarket.
Release a genuine Clojure or JVM client library with a POM, description, homepage and source metadata.
Create your public package repository for genuine releases and complete its namespace, description, licence and source/homepage metadata.
Publish a genuine iOS or macOS your tool SDK and set homepage/source URLs in its podspec.
Publish a genuine Perl module or CLI through PAUSE with project URLs and clear distribution documentation.
After releasing a genuinely Django-relevant open-source component, sign in and add its GitHub or GitLab repository and accurate project links.
Build an ESP-IDF privacy, credential-safety, secure-logging, or local-processing component, add manifest, license, docs, examples, and publish it through the registry workflow.
Publish your genuine versioned Nix flake under the correct GitHub owner and maintain its README and project links.
Submit your real maintained open-source release with accurate categories and project metadata.
Create a founder/developer portfolio, pin your tool repository/project and add the official website link.
Release a useful Haskell library or command-line client with homepage, source and bug-report metadata.
Release a useful Haxe SDK or privacy utility and set haxelib.json's URL to your relevant documentation page.
Create a truthful scholarly profile and deposit an original privacy, accessibility, or digital-humanities paper or teaching resource with its related your tool URL.
Create a useful Lua client or helper, publish its rockspec and include homepage, license and source links.
Release your reusable -related security or privacy module from a correctly named public GitHub repository.
Submit your maintained open-source component for community review.
Publish and maintain a tested Scoop manifest for your actual portable Windows CLI or app.
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.