APP ORIGIN LAB PRE-LAUNCH / NOINDEX

ABOUT / SCOPE AND OWNERSHIP

A research record, not another download catalog.

App Origin Lab examines how Android application artifacts connect to publishers, source repositories, signing identities, permissions, and observable behavior.

01 / PURPOSE

Why this site exists

App pages often collapse several different questions into one label: where a file came from, whether it can update an existing installation, what capabilities it requests, and whether anyone tested its behavior. This project keeps those questions separate and attaches dated evidence to each answer.

The intended output is a small body of reproducible studies, comparisons, evidence dossiers, and lookup data. The site does not host APK files and does not issue blanket “safe” or “unsafe” verdicts.

02 / DISCLOSURE

What “independent” means here

App Origin Lab is editorially independent from the developers and distributors it studies. It is not separately owned from every related web property: the site shares an operator and infrastructure with Acknosoft, TigrinhoAPK, 2113 Apps, and MSCTO.

Measurements collected for those properties may become research inputs here, but they do not become publishable conclusions automatically. Each App Origin Lab page needs its own question, source record, method, limitations, and review. References to related sites are disclosed and are not treated as third-party endorsements.

03 / BOUNDARIES

Claims this project will not make

  • A matching hash identifies the same bytes; it does not prove that software is harmless.
  • A matching signing certificate can support an update-continuity claim; it does not prove who currently controls the key.
  • Static code or manifest evidence does not prove that a behavior occurred on a device.
  • An absent tracker-library indicator does not prove that an app sends no data.
  • Hands-on performance, battery, or usability claims require a documented device test.
04 / CONTACT

Contact the lab