EmulatorEvidence 1.0.0 API


public final class EmulatorEvidence

What the heuristic found, so a verdict can be explained rather than asserted.

Field Summary

Fields
Modifier and Type	Field	Description
`private final Boolean`	`isEmulator`
`private final List<String>`	`all`
`private final List<String>`	`tiered`
`private final List<String>`	`strong`
`private final List<String>`	`weak`
`private final List<String>`	`context`

Constructor Summary

Constructors
Constructor	Description
`EmulatorEvidence(List<String> strong, List<String> weak, List<String> context)`

Method Summary

Modifier and Type	Method	Description
`final Boolean`	`getIsEmulator()`
`final List<String>`	`getAll()`
`final List<String>`	`getTiered()`
`final List<String>`	`getStrong()`
`final List<String>`	`getWeak()`
`final List<String>`	`getContext()`	Observed, reported for triage, and DELIBERATELY NOT COUNTED.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - EmulatorEvidence
```
EmulatorEvidence(List<String> strong, List<String> weak, List<String> context)
```
- Method Detail
  - getIsEmulator
```
 final Boolean getIsEmulator()
```
  - getAll
```
 final List<String> getAll()
```
  - getTiered
```
 final List<String> getTiered()
```
  - getStrong
```
 final List<String> getStrong()
```
  - getWeak
```
 final List<String> getWeak()
```
  - getContext
```
 final List<String> getContext()
```
    Observed, reported for triage, and DELIBERATELY NOT COUNTED.
    A third bucket exists because "we looked and saw this" and "this counts towards a verdict" are different claims, and collapsing them is how a false positive gets shipped. See telephony:absent below.