
Product
Introducing Tier 1 Reachability: Precision CVE Triage for Enterprise Teams
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
Cypress test parser that can extract test structure, and Cypress Command definitions and usage.
scryo find <command_name> <files_or_dirs>
This will parse js file(s) in the given files/directories, and print out the locations where:
Cypress.Command.add("cmdName", ...)
cy.cmdName(...)
or even cy.anotherCmd(...).cmdName(...)
.Example Usage:
[me@home]$ npx scryo find expectErrorSnackbar ./cypress
👀 Found definition of Cypress command "expectErrorSnackbar":
at (/Users/shawn/app/cypress/support/assertions.js:63:1)
🔍 Found 2 place(s) where cy.expectErrorSnackbar was used:
🔗 cy.navigateToLogin().goOffline().submitLogin().expectErrorSnackbar()
at (/Users/shawn/app/cypress/e2e/login/basicLogin.js:28:8)
🔗 cy.navigateToLogin().patchNetworkResponse().submitLogin().expectErrorSnackbar()
at (/Users/shawn/app/cypress/e2e/login/basicLogin.js:789:8)
scryo dump <files_or_dirs>
This will parse js file(s) in the given files/directories and emit the parsed content as JSON to stdout. This output will allow one to write reasonably complex validation rules without having to worry about source parsing.
Examples of validations than can be implemented with minimal effort:
The output will be in the following format, with an entry for every parsed file:
{
"path/to/file.js": {
"used": [], // Array of CommmandUseObj (see definition below)
"added": [], // Array of CommmandAddObj (see definition below)
"tests": [] // Array of TestObj (see definition below)
"hooks": {
"before": [], // Array of HookObj (see definition below)
"beforeEach": [], // Array of HookObj (see definition below)
"after": [], // Array of HookObj (see definition below)
"afterEach": [] // Array of HookObj (see definition below)
},
"errors": [], // Array of DeferredErrorObj, for issues that should not stop parsing but worth noting
// If Qwil Extension enabled
"scenarios": [], // Array of ScenarioObj (see definition below)
}
}
"used"
will list out all the Cypress commands used in that file"added"
will list out all the Cypress commands added in that file"tests"
will list out all the Cypress tests defined in that fileCommmandUseObj
:
{
"name": String, // name of the cy command used
"start": Number, // char offset in file where usage started
"end": Number, // char offset in file where usage ended
"arguments": Array[CommandArgObj], // type and char offsets for command arguments
"literalArguments"?: Object, // Actual values of arguments if they can be evaluated statically, indexed by argument index
"chain": Array[String], // chain of cy calls leading to this.
// e.g cy.a().b().c() will result in {"chain": ["a", "b"], "name": "c"}
}
CommandArgObj
:
{
"type": String, // node type for the argument, e.g. "ObjectExpression", "ArrowFunctionExpression", etc
"start": Number, // char offset in file where that argument started
"end": Number, // char offset in file where that argument ended
}
FuncCallObj
:
{
"name": String, // name of non-cy function call
"start": Number, // char offset in file where function call started. For dotted or chained calls, this points to
// beginning of the func identifier i.e. in the case of "hello.kitty()", start would point to "k"
"rootStart": Number, // this points to actual start i.e. in the case of "hello.kitty()", start would point to "h"
"end": Number, // char offset in file where function call ended
"arguments": Array[CommandArgObj], // type and char offsets for function call arguments
"literalArguments"?: Object, // Actual values of arguments if they can be evaluated statically, indexed by argument index
}
Note that if the function call was part of a chain of calls, "name" would capture that chain. For example:
assertSomething(); // name = "assertSomething"
this.setup(); // name = "this.setup"
api({ sync: false }).myFuncCall(/* params */); // name = "api().myFuncCall"
someLib.init().helpers.doSomething().decode(); // name = "someLib.init().helpers.doSomething().decode"
CommmandAddObj
:
{
"name": String, // name of the Cypress command added
"start": Number, // char offset in file where definition started
"end": Number, // char offset in file where definition ended
"cyMethodsUsed": Array[CommmandUseObj], // cy methods used within the implementation of this command
"otherFuncCalls": Array[FuncCallObj], // function calls (excluding cy.*) within the implementation of this command
}
TestObj
:
{
"scope": Array[ScopeObj], // Describes nesting scope
"start": Number, // char offset in file where definition started
"end": Number, // char offset in file where definition ended
"funcStart": Number, // char offset in file where definition of test implementation function started
"funcEnd": Number, // char offset in file where definition of test implementation function ended
"cyMethodsUsed": Array[CommmandUseObj], // cy methods used within the implementation of this test
"otherFuncCalls": Array[FuncCallObj], // function calls (excluding cy.*) within the implementation of this command
"skip"?: Boolean, // If this test was effectively skipped, either by it.skip or describe.skip on parent scope
"only"?: Boolean, // If this test was effectively set to "only", either by it.only or describe.only on parent scope
}
HookObj
:
{
"scope": Array[ScopeObj], // Describes nesting scope
"start": Number, // char offset in file where definition started
"end": Number, // char offset in file where definition ended
"funcStart": Number, // char offset in file where definition of test implementation function started
"funcEnd": Number, // char offset in file where definition of test implementation function ended
"cyMethodsUsed": Array[CommmandUseObj], // cy methods used within the implementation of this test
"otherFuncCalls": Array[FuncCallObj], // function calls (excluding cy.*) within the implementation of this command
}
ScopeObj
:
{
"func": "it" | "it.only" | "it.skip" | "describe" | "describe.only" | "describe.skip",
"name": String, // Text description
"start": Number, // char offset in file where definition started
"end": Number, // char offset in file where definition ended
"skip"?: Boolean, // If .skip
"only"?: Boolean, // If .only
}
DeferredErrorObj
:
{
"message": String, // Error message
"loc": Number, // char offset in file where error was detected
}
Example Usage:
[me@home]$ npx scryo dump cypress/e2e/login/errorConditions.js
Where the file contains:
describe("Login", () => {
describe("Error conditions", () => {
beforeEach(() => {
const params = utils.getNavParams();
cy.navigateToLogin(params);
})
it("should show error snackbar on submit if offline", () => {
cy.goOffline()
.submitLogin({ username: "bob", password: "builder" })
.expectErrorSnackbar();
})
})
})
We expected to get:
{
"test.js": {
"added": [],
"used": [
{
"name": "navigateToLogin",
"start": 140,
"end": 163,
"arguments": [
{
"type": "Identifier",
"start": 156,
"end": 162
}
],
"chain": []
},
{
"name": "goOffline",
"start": 248,
"end": 259,
"arguments": [],
"chain": []
},
{
"name": "submitLogin",
"start": 269,
"end": 322,
"arguments": [
{
"type": "ObjectExpression",
"start": 281,
"end": 321
}
],
"literalArguments": {
"0": {
"username": "bob",
"password": "builder"
}
},
"chain": [
"goOffline"
]
},
{
"name": "expectErrorSnackbar",
"start": 332,
"end": 353,
"arguments": [],
"chain": [
"goOffline",
"submitLogin"
]
}
],
"tests": [
{
"scope": [
{
"name": "Login",
"func": "describe",
"start": 0,
"end": 369
},
{
"name": "Error conditions",
"func": "describe",
"start": 28,
"end": 366
},
{
"name": "should show error snackbar on submit if offline",
"func": "it",
"start": 177,
"end": 361
}
],
"start": 177,
"end": 361,
"funcStart": 231,
"funcEnd": 360,
"cyMethodsUsed": [
{
"name": "goOffline",
"start": 248,
"end": 259,
"arguments": [],
"chain": []
},
{
"name": "submitLogin",
"start": 269,
"end": 322,
"arguments": [
{
"type": "ObjectExpression",
"start": 281,
"end": 321
}
],
"literalArguments": {
"0": {
"username": "bob",
"password": "builder"
}
},
"chain": [
"goOffline"
]
},
{
"name": "expectErrorSnackbar",
"start": 332,
"end": 353,
"arguments": [],
"chain": [
"goOffline",
"submitLogin"
]
}
],
"otherFuncCalls": []
}
],
"hooks": {
"before": [],
"beforeEach": [
{
"scope": [
{
"name": "Login",
"func": "describe",
"start": 0,
"end": 369
},
{
"name": "Error conditions",
"func": "describe",
"start": 28,
"end": 366
}
],
"start": 69,
"end": 171,
"funcStart": 80,
"funcEnd": 170,
"cyMethodsUsed": [
{
"name": "navigateToLogin",
"start": 140,
"end": 163,
"arguments": [
{
"type": "Identifier",
"start": 156,
"end": 162
}
],
"chain": []
}
],
"otherFuncCalls": [
{
"name": "utils.getNavParams",
"start": 115,
"rootStart": 109,
"end": 129,
"arguments": []
}
]
}
],
"after": [],
"afterEach": []
},
"errors": []
}
}
FAQs
Parses cypress test files to extract Command definition/usage and tests
We found that scryo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.