Methodology
How entries are researched, sourced, dated and maintained.
Source hierarchy
Claims are taken from sources in this order of preference:
- Vendor documentation and release notes.
- Official repositories and the GitHub API, for open-source tools.
- Reputable press and published research.
- Leaked documents, only when they have been reported on by reputable outlets, and then always dated and attributed to the outlet that reported them.
Every capability and limitation on a tool page carries a link to the source it came from. If no source could be opened and read, the claim is left out. Where a claim is the vendor's own and cannot be independently confirmed, the entry says so. Unknown is a valid answer: a missing price or date means it could not be established, not that it is zero.
What "last activity" means
Last activity is the date of the most recent public sign that a product is maintained or sold, such as a release, a release-notes entry or a repository commit, with a note saying which and a link to it. It is not a measure of quality, and it is not a guarantee that a tool works with current devices.
How GitHub activity is checked
For entries with a public repository, a script queries the GitHub API for the repository and its latest release and records stars, licence, the last push date, whether the repository is archived and the latest release tag and date. The result is stored with the date it was checked. If the API cannot be reached, the previous values are kept and the check date is not advanced.
Locked and encrypted devices
Claims about bypassing or extracting from locked, encrypted, before-first-unlock (BFU) or after-first-unlock (AFU) devices are the most sensitive and the most perishable. They are stated as point-in-time claims, attributed to a named source and dated, for example a vendor statement or a named outlet's reporting on a document as of a given month. A dated or leaked support matrix is never generalised into a statement of current capability.
Review cadence
Every entry shows the date it was reviewed. Entries that have not been reviewed for more than 180 days are flagged during maintenance for a fresh check.
How entries are maintained
The site follows a content-as-code approach: each tool is a structured file and each guide a Markdown file in a version-controlled repository. A validation step checks required fields, allowed values, date formats, that every capability and limitation has an https source, that related entries exist and that there are no duplicates. A build with a validation error does not ship.
Corrections policy
Errors are corrected in the entry, and the review date is updated. If you are a vendor, maintainer or reader and believe an entry is inaccurate or out of date, a correction that points to a primary source will be applied. Vendors cannot buy changes, removals or placement. Send corrections to corrections@mobiledfir.com with a link to a primary source. See also about.