mirror of
https://github.com/QM4RS/FridaBox.git
synced 2026-09-16 14:12:11 +02:00
49 lines
1.5 KiB
YAML
49 lines
1.5 KiB
YAML
name: Research or feature proposal
|
|
description: Propose a scoped capability or research direction.
|
|
title: "[Proposal]: "
|
|
labels: [enhancement]
|
|
body:
|
|
- type: checkboxes
|
|
attributes:
|
|
label: Scope
|
|
options:
|
|
- label: This proposal is for authorized research and defensive testing.
|
|
required: true
|
|
- label: I reviewed the architecture and current limitations.
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Problem
|
|
description: What concrete limitation or workflow gap should be addressed?
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
attributes:
|
|
label: Research area
|
|
options:
|
|
- Frida visibility reduction
|
|
- /proc and process-map consistency
|
|
- Virtual-environment fidelity
|
|
- Android or vendor compatibility
|
|
- Import, integrity, or ABI handling
|
|
- Controller and developer tooling
|
|
- Product UI and accessibility
|
|
- Documentation or validation
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Proposed boundary
|
|
description: Which host, virtual runtime, Gadget, controller, or UI component changes?
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Acceptance evidence
|
|
description: Describe the tests and device proof that would demonstrate success.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Alternatives and risks
|