@take2identity/verosint 0.2.61 → 0.2.62
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,6 +14,7 @@
|
|
|
14
14
|
## Installation
|
|
15
15
|
|
|
16
16
|
Use the `verosint` tool to:
|
|
17
|
+
|
|
17
18
|
* Tag account's using the SignalPrint tagging endpoint to distinguish identities
|
|
18
19
|
* Lookup account's and find identifiers, signals, fraud labels, and related accounts
|
|
19
20
|
* Send events to the SignalPrint endpoint to create a map of identities and access history.
|
|
@@ -155,7 +156,7 @@ Responses are provided in the JSON format on the standard output.
|
|
|
155
156
|
|
|
156
157
|
##### Examples
|
|
157
158
|
|
|
158
|
-
###### 2. Evaluate an IPv6 address, a phone number and an email address for a
|
|
159
|
+
###### 2. Evaluate an IPv6 address, a phone number and an email address for a Rule Set
|
|
159
160
|
|
|
160
161
|
```shell
|
|
161
162
|
verosint evalute rule ip:2607:fb91:1296:c7dc:a0c4:25a9:ac7a:4384 email:user@example.com phone:15123944240 --ruleSetUuid 4f5ab21b-984c-455e-b889-b6b0272a4567
|
|
@@ -185,7 +186,7 @@ This example evaluates the `babs@jensen.com` email address against the rule defi
|
|
|
185
186
|
in the `mfarule.json` file.
|
|
186
187
|
|
|
187
188
|
```shell
|
|
188
|
-
verosint evaluate rule email:babs@jensen.com --
|
|
189
|
+
verosint evaluate rule email:babs@jensen.com --ruleSetFile mfarule.json
|
|
189
190
|
```
|
|
190
191
|
|
|
191
192
|
##### 5. Check if an IP address is within 100 kilometers of Austin, TX using a local rule set
|
|
@@ -214,7 +215,7 @@ verosint evaluate rules ip:104.16.44.99
|
|
|
214
215
|
|
|
215
216
|
#### Batch Evaluation
|
|
216
217
|
|
|
217
|
-
Use input files to evaluate multiple sets of identifiers against rules.
|
|
218
|
+
Use input files to evaluate multiple sets of identifiers against rules.
|
|
218
219
|
Batch commands can use input and output files in CSV or
|
|
219
220
|
LDIF format, and can produce a report file formatted as JSON.
|
|
220
221
|
|
|
@@ -258,7 +259,7 @@ The timestamp is expected to be in the
|
|
|
258
259
|
[RFC3339](https://www.rfc-editor.org/rfc/rfc3339) format. For example:
|
|
259
260
|
`2019-01-22T03:56:17+03:30`.
|
|
260
261
|
|
|
261
|
-
The type can be one of:
|
|
262
|
+
The type can be one of:
|
|
262
263
|
LOGIN_SUCCESS, LOGIN_FAILED, MFA_SUCCESS, MFA_FAILED, or VERIFICATION_SUCCESS
|
|
263
264
|
|
|
264
265
|
##### Examples for Signal Print
|