
Security News
/Research
Popular node-ipc npm Package Infected with Credential Stealer
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.
@pothos/plugin-complexity
Advanced tools
A Pothos plugin for defining and limiting complexity of queries
This plugin allows you to define complexity of fields and limit the maximum complexity, depth, and breadth of queries.
yarn add @pothos/plugin-complexity
import ComplexityPlugin from '@pothos/plugin-complexity';
const builder = new SchemaBuilder({
plugins: [ComplexityPlugin],
});
To limit query complexity you can specify a maximum complexity either in the builder setup, or when building the schema:
const builder = new SchemaBuilder({
plugins: [ComplexityPlugin],
defaultComplexity: 1,
defaultListMultiplier: 10,
complexity: {
limit: {
complexity: 500,
depth: 10,
breadth: 50,
},
// or
limit: (ctx) => ({
complexity: 500,
depth: 10,
breadth: 50,
}),
},
});
// or
const schema = builder.toSchema({
complexity: {
limit: {
complexity: 500,
depth: 10,
breadth: 50,
},
},
});
(args, ctx, field) => { complexity: number, multiplier: number} | number): default complexity
calculation for fields. defaultComplexity and defaultListMultiplier will not be used if this
is set.number) defines the default complexity for every field in the
schemanumber) defines a default complexity multiplier for a list
fields sub selectionslimit is a function
function) defines the error to throw when the query complexity
exceeds the limit. The function is passed the errorKind (depth, breadth, or complexity), the
result (with the depth, breadth, complext, and max values), and a GraphQL info object. It should
return (or throw) an error, or a an error message as a stringComplexity is calculated before resolving root any root level fields (query, mutation, subscription), and is based purely on the shape of the query before execution begins.
The complexity of a query is the sum of the complexity of each selected field. If a field has sub-selections, the complexity of its sub-selections are multiplied by a fields multiplier, and then added to the fields own complexity. The default multiplier for fields is 1, and 10 for list fields. This multiplier is meant to the n+1 complexity of list fields.
The following query has a complexity of 131 (assuming we are using the default options), a depth
of 3, and a breadth of 5:
query {
posts {
# complexity = 131 (posts + 10 * (2 + 11))
author {
# complexity = 2 (author + 1 * name)
name # complexity = 1, depth: 3
}
comments {
# complexity = 11 (comments + 10 * comment)
comment # complexity = 1, depth: 3
}
}
}
You can set a custom complexity value on any field:
builder.queryFields((t) => ({
posts: t.field({
type: [Post],
complexity: 20,
}),
}));
The complexity option can also set the multiplier for a field:
builder.queryFields((t) => ({
posts: t.field({
type: [Post],
complexity: { field: 5, multiplier: 20 },
}),
}));
A fields complexity can also be based on the fields arguments, or the context value:
builder.queryFields((t) => ({
posts: t.field({
type: [Post],
args: {
limit: t.arg.int(),
},
// base multiplier on how many posts are being requested
complexity: (args, ctx) => ({ field: 5, multiplier: args.limit ?? 5 }),
}),
}));
complexityFromQuery(query, options)Returns the query complexity for a given GraphQL query.
const complexity = complexityFromQuery(query, {
schema: schema,
// Complexity can be calculated based on the context and arguments,
// so you may need to provide valid values for the context and arguments.
// Both are optional, and will default to empty objects.
context: {},
variables: {},
});
FAQs
A Pothos plugin for defining and limiting complexity of queries
We found that @pothos/plugin-complexity demonstrated a healthy version release cadence and project activity because the last version was released less than 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.

Security News
/Research
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.

Security News
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.

Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.