Gathering detailed insights and metrics for async-json-schema-traverse
Gathering detailed insights and metrics for async-json-schema-traverse
Traverse JSON Schema passing each schema object to callback
Installations
npm install async-json-schema-traverseDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Node Version
10.19.0
NPM Version
6.13.4
Score
72.1
Supply Chain
97.7
Quality
75.3
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Languages
1
JavaScript
JavaScript (100%)
Developer
moderncrazy
Download Statistics
Total Downloads
13,696
Last Day
9
Last Week
898
Last Month
4,398
Last Year
13,072
GitHub Statistics
MIT License
47 Commits
1 Branches
1 Contributors
Updated on Apr 04, 2021
Bundle Size
1.35 kB
Minified
645.00 B
Minified + Gzipped
Maintainers
1
Package Meta Information
Latest Version
1.0.1
Package Id
async-json-schema-traverse@1.0.1
Unpacked Size
8.59 kB
Size
3.37 kB
File Count
5
NPM Version
6.13.4
Node Version
10.19.0
Total Downloads
Cumulative downloads
Total Downloads
13,696
Dev Dependencies
4
async-json-schema-traverse
Traverse JSON Schema passing each schema object to callback (fork json-schema-traverse)
Install
npm install async-json-schema-traverse
Usage
1const traverse = require('async-json-schema-traverse'); 2const schema = { 3 properties: { 4 foo: {type: 'string'}, 5 bar: {type: 'integer'} 6 } 7}; 8 9await traverse(schema, {cb}); 10// cb is called 3 times with: 11// 1. root schema 12// 2. {type: 'string'} 13// 3. {type: 'integer'} 14 15// Or: 16 17await traverse(schema, {cb: {pre, post}}); 18// pre is called 3 times with: 19// 1. root schema 20// 2. {type: 'string'} 21// 3. {type: 'integer'} 22// 23// post is called 3 times with: 24// 1. {type: 'string'} 25// 2. {type: 'integer'} 26// 3. root schema 27
Callback function cb is called for each schema object (not including draft-06 boolean schemas), including the root schema, in pre-order traversal. Schema references ($ref) are not resolved, they are passed as is. Alternatively, you can pass a {pre, post} object as cb, and then pre will be called before traversing child elements, and post will be called after all child elements have been traversed.
Callback is passed these parameters:
- schema: the current schema object
- JSON pointer: from the root schema to the current schema object
- root schema: the schema passed to
traverseobject - parent JSON pointer: from the root schema to the parent schema object (see below)
- parent keyword: the keyword inside which this schema appears (e.g.
properties,anyOf, etc.) - parent schema: not necessarily parent object/array; in the example above the parent schema for
{type: 'string'}is the root schema - index/property: index or property name in the array/object containing multiple schemas; in the example above for
{type: 'string'}the property name is'foo'
Traverse objects in all unknown keywords
1const traverse = require('async-json-schema-traverse'); 2const schema = { 3 mySchema: { 4 minimum: 1, 5 maximum: 2 6 } 7}; 8 9traverse(schema, {allKeys: true, cb}); 10// cb is called 2 times with: 11// 1. root schema 12// 2. mySchema
Without option allKeys: true callback will be called only with root schema.
Enterprise support
json-schema-traverse package is a part of Tidelift enterprise subscription - it provides a centralised commercial support to open-source software users, in addition to the support provided by software maintainers.
Security contact
To report a security vulnerability, please use the Tidelift security contact. Tidelift will coordinate the fix and disclosure. Please do NOT report security vulnerability via GitHub issues.
License
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/moderncrazy/json-schema-traverse/build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/moderncrazy/json-schema-traverse/build.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/moderncrazy/json-schema-traverse/build.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/moderncrazy/json-schema-traverse/publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/moderncrazy/json-schema-traverse/publish.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/build.yml:24
- Warn: npmCommand not pinned by hash: .github/workflows/publish.yml:17
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 0 out of 2 npmCommand dependencies pinned
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/build.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Score
3.4
/10
Last Scanned on 2025-06-23
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More