Skip to content
Download.sa Download.sa
Install Download.sa on iPhone or iPad: tap the Share button, then choose “Add to Home Screen”.

Trust Network

Five levels of real checks — each with its source and date. Not a certification.

A trust profile lists which of our checks passed, with the source and date of each. It is not a certification, an approval or a guarantee that the software is harmless.

How a profile is built

  1. 1Every check reads facts the platform already records: verification of the publisher, the link checker, checksums, signatures, file fingerprints, vulnerability feeds and end-of-life data.
  2. 2Each check has one of four statuses: verified, partial, not verified or unknown.
  3. 3Profiles are recomputed every day and after a developer asks for a re-check; every change of a level is kept in the history.
  4. 4Nobody can type a status by hand, and plans, advertising or payments never change a result.

A level is verified when all its required checks are verified and none of its checks reports a problem. Supporting checks add evidence but are not required.

The four statuses

Verified
The check passed with the evidence shown.
Partial
Some evidence exists, but not all of what the check needs.
Not verified
The check did not pass, or the evidence is missing.
Unknown
We have no data for this check yet.

The five levels and their checks

1

Level 1

Publisher identity

Who publishes the software: a publisher verified by domain (DNS TXT), company e-mail or staff review, and the developer's ownership claim of the listing.

Checks

  • Verified publisher Required The publisher record is verified (domain DNS record, website file, company e-mail, code signing, official repository or staff review).
  • Domain or company e-mail Supporting The publisher proved control of its website domain with a DNS TXT record or a link sent to an address at that domain.
  • Ownership claim Supporting The developer who manages this listing proved ownership (DNS, website file, meta tag, repository file or staff review); automatic proofs are re-checked monthly.
2

Level 2

Official source

Where the files come from: download links on the publisher's official domains or admin-trusted hosts, and the link checker's safety results (redirects, shorteners, look-alike hosts, HTTPS).

Checks

  • Official download hosts Required Every download link (after redirects) is on the homepage or publisher domain, or on a host the platform trusts (for example GitHub Releases).
  • Link safety Required The link checker found no shorteners, look-alike or mixed-script hosts, credentials in the URL or unofficial destinations.
  • HTTPS downloads Supporting All download links use HTTPS.
3

Level 3

Release integrity

Whether the files are the ones the publisher released: checksums published by the publisher, digital-signature verification, and files that cannot be replaced after approval and are monitored at their official URL.

Checks

  • Publisher checksums Required Each file has a SHA-256 checksum published by the publisher (package manifest or vendor checksum list) and no checksum list mismatch.
  • Immutable, monitored files Required Files of the approved release cannot be replaced, and the hourly monitor fingerprints them at their official URL with no unreviewed change.
  • Digital signature Supporting Authenticode, a detached PGP signature or a vendor checksum list was verified on the isolated scan worker.
4

Level 4

Security and support

Known vulnerabilities of the latest version and how quickly fixes shipped, whether the version is still supported (end-of-life data) and how regularly new releases appear.

Checks

  • Open vulnerabilities Required No known vulnerability affects the latest version, according to the configured feeds (OSV, NVD, CISA KEV).
  • Update cadence Required The latest release is recent compared with the software's own release history.
  • Supported version Supporting The latest version belongs to a release cycle that endoflife.date lists as supported.
  • Patch delay Supporting Median days between a vulnerability's publication and the first release that fixes it.
5

Level 5

Continuous monitoring

How recently the platform re-checked the files (integrity monitor), the download links (link checker) and the vulnerability feeds (OSV / NVD / CISA KEV).

Checks

  • Integrity monitoring Required The integrity monitor checked every downloadable file recently.
  • Link monitoring Required The link checker checked every download link recently.
  • Vulnerability monitoring Required A vulnerability feed is configured and was synchronised recently without an error for this software.

Monitoring windows: recent = within 2 days, out of date = older than 14 days.

Install Download.sa on your device

Open it from your home screen in one tap, in its own window.

Install Download.sa on iPhone or iPad: tap the Share button, then choose “Add to Home Screen”.