| commit | 9d90763de4dc9c42c9488b22d696691b3b8dfb3f | [log] [tgz] |
|---|---|---|
| author | Chris Dombroski <cdombroski@google.com> | Mon Sep 15 22:34:25 2025 +0000 |
| committer | Chris Dombroski <cdombroski@google.com> | Mon Oct 20 22:06:58 2025 +0000 |
| tree | ac2a75f4a7af333a734caa75ea6505f6997df95e | |
| parent | 0c0eb852a69ab4dc27a868054ea8a01c49c4932e [diff] |
Add READMEs to the examples and templates Bug: 441727732 Test: none Change-Id: I138dee06ba6791eacbffc7f916f7abf84c65f651
This repository contains standalone examples and templates for creating Android Vulnerability Reward Program (VRP) submissions using the AutoRepro framework.
The goal of these projects is to help you write effective, automatically reproducible proofs-of-concept.
To get started, choose the project that best fits your proof-of-concept:
example/: A comprehensive project that demonstrates all major AutoRepro features working together, including multiple device-side apps and a native (NDK) test. This is a good resource to see how different parts can interact.
templates/: A collection of minimal, use-case-specific projects. We recommend starting with one of these templates.
Throughout the projects, you will find variants of the string autorepro_placeholder used in package names, resource files, and other identifiers.
When your submission is processed, our internal tooling performs a find-and-replace on this token to assign your test a unique name for translation into the Android build system.
Please do not modify the autorepro_placeholder string. Leave it as-is in all file names, package names, and resource paths.
For full documentation on writing an AutoRepro test, please see the public documentation.