===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
node-ajv-6.12.6/FAQ.md-102-
node-ajv-6.12.6/FAQ.md:103:There were many conversations about the meaning of `$ref` in [JSON Schema GitHub organisation](https://github.com/json-schema-org). The consensus is that while it is possible to treat `$ref` as schema inclusion with two caveats (above), this interpretation is unnecessary complex. A more efficient approach is to treat `$ref` as a delegation, i.e. a special keyword that validates the current data instance against the referenced schema. The analogy with programming languages is that `$ref` is a function call rather than a macro. See [here](https://github.com/json-schema-org/json-schema-spec/issues/279), for example.
node-ajv-6.12.6/FAQ.md-104-
node-ajv-6.12.6/FAQ.md-105-
node-ajv-6.12.6/FAQ.md:106:##### How can I generate a schema where `$ref` keywords are replaced with referenced schemas?
node-ajv-6.12.6/FAQ.md-107-
##############################################
node-ajv-6.12.6/FAQ.md-109-
node-ajv-6.12.6/FAQ.md:110:1. Traverse schema (e.g. with json-schema-traverse) and replace every `$ref` with the referenced schema.
node-ajv-6.12.6/FAQ.md-111-2. Use a specially constructed JSON Schema with a [custom keyword](https://github.com/ajv-validator/ajv/blob/master/CUSTOM.md) to traverse and modify your schema.
##############################################
node-ajv-6.12.6/KEYWORDS.md-672-
node-ajv-6.12.6/KEYWORDS.md:673:The same can be achieved with `enum` keyword using the array with one item. But `const` keyword is more than just a syntax sugar for `enum`. In combination with the [$data reference](https://github.com/ajv-validator/ajv#data-reference) it allows to define equality relations between different parts of the data. This cannot be achieved with `enum` keyword even with `$data` reference because `$data` cannot be used in place of one item - it can only be used in place of the whole array in `enum` keyword.
node-ajv-6.12.6/KEYWORDS.md-674-
##############################################
node-ajv-6.12.6/README.md-318-- `title` and `description`: information about the data represented by that schema
node-ajv-6.12.6/README.md:319:- `$comment` (NEW in draft-07): information for developers. With option `$comment` Ajv logs or passes the comment string to the user-supplied function. See [Options](#options).
node-ajv-6.12.6/README.md-320-- `default`: a default value of the data instance, see [Assigning defaults](#assigning-defaults).
##############################################
node-ajv-6.12.6/README.md-365-
node-ajv-6.12.6/README.md:366:You can structure your validation logic across multiple schema files and have schemas reference each other using `$ref` keyword.
node-ajv-6.12.6/README.md-367-
##############################################
node-ajv-6.12.6/README.md-406-__Please note__:
node-ajv-6.12.6/README.md:407:- `$ref` is resolved as the uri-reference using schema $id as the base URI (see the example).
node-ajv-6.12.6/README.md-408-- References can be recursive (and mutually recursive) to implement the schemas for different data structures (such as linked lists, trees, graphs, etc.).
##############################################
node-ajv-6.12.6/README.md-417-
node-ajv-6.12.6/README.md:418:With `$data` option you can use values from the validated data as the values for the schema keywords. See [proposal](https://github.com/json-schema-org/json-schema-spec/issues/51) for more information about how it works.
node-ajv-6.12.6/README.md-419-
node-ajv-6.12.6/README.md:420:`$data` reference is supported in the keywords: const, enum, format, maximum/minimum, exclusiveMaximum / exclusiveMinimum, maxLength / minLength, maxItems / minItems, maxProperties / minProperties, formatMaximum / formatMinimum, formatExclusiveMaximum / formatExclusiveMinimum, multipleOf, pattern, required, uniqueItems.
node-ajv-6.12.6/README.md-421-
##############################################
node-ajv-6.12.6/README.md-464-
node-ajv-6.12.6/README.md:465:`$data` reference is resolved safely - it won't throw even if some property is undefined. If `$data` resolves to `undefined` the validation succeeds (with the exclusion of `const` keyword). If `$data` resolves to incorrect type (e.g. not "number" for maximum keyword) the validation fails.
node-ajv-6.12.6/README.md-466-
##############################################
node-ajv-6.12.6/README.md-469-
node-ajv-6.12.6/README.md:470:With the package [ajv-merge-patch](https://github.com/ajv-validator/ajv-merge-patch) you can use the keywords `$merge` and `$patch` that allow extending JSON Schemas with patches using formats [JSON Merge Patch (RFC 7396)](https://tools.ietf.org/html/rfc7396) and [JSON Patch (RFC 6902)](https://tools.ietf.org/html/rfc6902).
node-ajv-6.12.6/README.md-471-
node-ajv-6.12.6/README.md:472:To add keywords `$merge` and `$patch` to Ajv instance use this code:
node-ajv-6.12.6/README.md-473-
##############################################
node-ajv-6.12.6/README.md-479-
node-ajv-6.12.6/README.md:480:Using `$merge`:
node-ajv-6.12.6/README.md-481-
##############################################
node-ajv-6.12.6/README.md-496-
node-ajv-6.12.6/README.md:497:Using `$patch`:
node-ajv-6.12.6/README.md-498-
##############################################
node-ajv-6.12.6/README.md-526-
node-ajv-6.12.6/README.md:527:The properties `source` and `with` in the keywords `$merge` and `$patch` can use absolute or relative `$ref` to point to other schemas previously added to the Ajv instance or to the fragments of the current schema.
node-ajv-6.12.6/README.md-528-
##############################################
node-ajv-6.12.6/README.md-613-
node-ajv-6.12.6/README.md:614:If your schema uses asynchronous formats/keywords or refers to some schema that contains them it should have `"$async": true` keyword so that Ajv can compile it correctly. If asynchronous format/keyword or reference to asynchronous schema is used in the schema without `$async` keyword Ajv will throw an exception during schema compilation.
node-ajv-6.12.6/README.md-615-
node-ajv-6.12.6/README.md:616:__Please note__: all asynchronous subschemas that are referenced from the current or other schemas should have `"$async": true` keyword as well, otherwise the schema compilation will fail.
node-ajv-6.12.6/README.md-617-
##############################################
node-ajv-6.12.6/README.md-621-
node-ajv-6.12.6/README.md:622:The compiled validation function has `$async: true` property (if the schema is asynchronous), so you can differentiate these functions if you are using both synchronous and asynchronous schemas.
node-ajv-6.12.6/README.md-623-
##############################################
node-ajv-6.12.6/README.md-1027-
node-ajv-6.12.6/README.md:1028:If the schema is asynchronous (has `$async` keyword on the top level) this method returns a Promise. See [Asynchronous validation](#asynchronous-validation).
node-ajv-6.12.6/README.md-1029-
##############################################
node-ajv-6.12.6/README.md-1065-
node-ajv-6.12.6/README.md:1066:If schema doesn't have `$schema` property, it is validated against draft 6 meta-schema (option `meta` should not be false).
node-ajv-6.12.6/README.md-1067-
node-ajv-6.12.6/README.md:1068:If schema has `$schema` property, then the schema with this id (that should be previously added) is used to validate passed schema.
node-ajv-6.12.6/README.md-1069-
##############################################
node-ajv-6.12.6/README.md-1225-- _verbose_: include the reference to the part of the schema (`schema` and `parentSchema`) and validated data in errors (false by default).
node-ajv-6.12.6/README.md:1226:- _$comment_ (NEW in Ajv version 6.0): log or pass the value of `$comment` keyword to a function. Option values:
node-ajv-6.12.6/README.md-1227- - `false` (default): ignore $comment keyword.
##############################################
node-ajv-6.12.6/README.md-1252-- _schemaId_: this option defines which keywords are used as schema URI. Option value:
node-ajv-6.12.6/README.md:1253: - `"$id"` (default) - only use `$id` keyword as schema URI (as specified in JSON Schema draft-06/07), ignore `id` keyword (if it is present a warning will be logged).
node-ajv-6.12.6/README.md:1254: - `"id"` - only use `id` keyword as schema URI (as specified in JSON Schema draft-04), ignore `$id` keyword (if it is present a warning will be logged).
node-ajv-6.12.6/README.md:1255: - `"auto"` - use both `$id` and `id` keywords as schema URI. If both are present (in the same schema object) and different the exception will be thrown during schema compilation.
node-ajv-6.12.6/README.md-1256-- _missingRefs_: handling of missing referenced schemas. Option values:
##############################################
node-ajv-6.12.6/README.md-1259- - `"fail"` - to log error and successfully compile schema but fail validation if this rule is checked.
node-ajv-6.12.6/README.md:1260:- _extendRefs_: validation of other keywords when `$ref` is present in the schema. Option values:
node-ajv-6.12.6/README.md:1261: - `"ignore"` (default) - when `$ref` is used other keywords are ignored (as per [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03#section-3) standard). A warning will be logged during the schema compilation.
node-ajv-6.12.6/README.md:1262: - `"fail"` (recommended) - if other validation keywords are used together with `$ref` the exception will be thrown when the schema is compiled. This option is recommended to make sure schema has no keywords that are ignored, which can be confusing.
node-ajv-6.12.6/README.md:1263: - `true` - validate all keywords in the schemas with `$ref` (the default behaviour in versions before 5.0.0).
node-ajv-6.12.6/README.md-1264-- _loadSchema_: asynchronous function that will be used to load remote schemas when `compileAsync` [method](#api-compileAsync) is used and some reference is missing (option `missingRefs` should NOT be 'fail' or 'ignore'). This function should accept remote schema uri as a parameter and return a Promise that resolves to a schema. See example in [Asynchronous compilation](#asynchronous-schema-compilation).
##############################################
node-ajv-6.12.6/README.md-1308-
node-ajv-6.12.6/README.md:1309:- _meta_: add [meta-schema](http://json-schema.org/documentation.html) so it can be used by other schemas (true by default). If an object is passed, it will be used as the default meta-schema for schemas that have no `$schema` keyword. This default meta-schema MUST have `$schema` keyword.
node-ajv-6.12.6/README.md:1310:- _validateSchema_: validate added/compiled schemas against meta-schema (true by default). `$schema` property in the schema can be http://json-schema.org/draft-07/schema or absent (draft-07 meta-schema will be used) or can be a reference to the schema previously added with `addMetaSchema` method. Option values:
node-ajv-6.12.6/README.md-1311- - `true` (default) - if the validation fails, throw the exception.
##############################################
node-ajv-6.12.6/README.md-1313- - `false` - skip schema validation.
node-ajv-6.12.6/README.md:1314:- _addUsedSchema_: by default methods `compile` and `validate` add schemas to the instance if they have `$id` (or `id`) property that doesn't start with "#". If `$id` is present and it is not unique the exception will be thrown. Set this option to `false` to skip adding schemas to the instance and the `$id` uniqueness check when these methods are used. This option does not affect `addSchema` method.
node-ajv-6.12.6/README.md-1315-- _inlineRefs_: Affects compilation of referenced schemas. Option values:
##############################################
node-ajv-6.12.6/README.md-1379-- `enum` - property `allowedValues` pointing to the array of values (the schema of the keyword).
node-ajv-6.12.6/README.md:1380:- `$ref` - property `ref` with the referenced schema URI.
node-ajv-6.12.6/README.md-1381-- `oneOf` - property `passingSchemas` (array of indices of passing schemas, null if no schema passes).
##############################################
node-ajv-6.12.6/lib/compile/formats.js-71- url: URL,
node-ajv-6.12.6/lib/compile/formats.js:72: email: /^[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*@(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?$/i,
node-ajv-6.12.6/lib/compile/formats.js-73- hostname: HOSTNAME,
##############################################
node-ajv-6.12.6/spec/tests/issues/27_1_recursive_raml_schema.json-141- "type": "string",
node-ajv-6.12.6/spec/tests/issues/27_1_recursive_raml_schema.json:142: "pattern": "^[a-zA-Z0-9!#$%^&*_\\-+{}|'.`~]+/[a-zA-Z0-9!#$%^&*_\\-+{}|'.`~]+$",
node-ajv-6.12.6/spec/tests/issues/27_1_recursive_raml_schema.json-143- "description": "The media types returned by API responses, and expected from API requests that accept a body, MAY be defaulted by specifying the mediaType property."
##############################################
node-ajv-6.12.6/spec/tests/issues/27_1_recursive_raml_schema.json-388- "patternProperties": {
node-ajv-6.12.6/spec/tests/issues/27_1_recursive_raml_schema.json:389: "^[a-zA-Z0-9!#$%^&*_\\-+{}|'.`~]+/[a-zA-Z0-9!#$%^&*_\\-+{}|'.`~]+$": {
node-ajv-6.12.6/spec/tests/issues/27_1_recursive_raml_schema.json-390- "$ref": "#/definitions/standardResponseBody"
##############################################
node-ajv-6.12.6/spec/tests/issues/28_escaping_pattern_error.json-8- "type": "string",
node-ajv-6.12.6/spec/tests/issues/28_escaping_pattern_error.json:9: "pattern": "^[a-zA-Z0-9!#$%^&*_\\-+{}|'.`~]+/[a-zA-Z0-9!#$%^&*_\\-+{}|'.`~]+$"
node-ajv-6.12.6/spec/tests/issues/28_escaping_pattern_error.json-10- }