sorona.xyz bug bounty programs
scorecard.dev Updated
Sorona.xyz runs one public program: a Sorona bug bounty paying up to $1,500.
- Top reward
- $1,500
- Sorona
- Programs
- 1
- 1 pays cash
- Targets in scope
- 8
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program sorona.xyz runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
OpenSSF Scorecard
Sorona · Bug bounty |
– | – | – | $100 | $1,500 | Partial | – | – | Open |
-
- Critical
- –
- High
- –
- Medium
- –
- Low
- $100
- Safe harbor
- Partial
Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.
What is in scope
8 targets. 5 excluded.
-
https://scorecard.dev
Web
-
Reports go to [email protected] under the Linux Foundation's standard security process. The one thing the project rules out by name is a disagreement about how a check scores a repository
Products and areas
-
scorecard-action, the GitHub Action wrapper that executes inside the CI of the repository being scored, with that repository's credentials in the environment
Products and areas
-
The command-line tool and its output handling, which is what maintainers and vendor-risk tooling actually invoke
Products and areas
-
The GitHub, GitLab and Azure DevOps API clients in full, covering how they authenticate and how they store, scope and log their tokens
Products and areas
-
The parsing libraries underneath those checks, including the YAML and probe paths that carry the two OSS-Fuzz harnesses (yaml_fuzzer.go and probes_fuzzer.go)
Products and areas
-
The signing and attestation path into the Scorecard results API and the public BigQuery dataset, where a forged or mis-attributed result poisons a dataset other tooling trusts
Products and areas
-
The whole check and probe layer, meaning every implementation that parses third-party repository content: GitHub Actions workflow YAML, Dockerfiles, dependency manifests and SBOMs, none of which Scorecard controls
Products and areas
No target matches. Try part of a host name, such as the company name.
Out of scope 5
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
Disagreements about check scoring methodology, which are policy debates rather than vulnerabilities
-
For the Google money specifically, anything reported but never patched upstream, since that pathway pays only on a merge
-
Non-exploitable crashes whose fix is a one-liner, which Google explicitly declines to reward on the patch rail
-
Patches over twelve months old, which Patch Rewards will not consider
-
The scorecard-webapp deployment as a hosted service, as distinct from the code in its repository
Recent changes
Reward and scope changes across every sorona.xyz program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
About this page
This page gathers every public program listed under scorecard.dev: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.
Something wrong or missing? Report a correction.