getRisksPreventedByUser
Get the users with the most security guidelines provided, with a count per guideline severity, sorted by total descending. The operation keeps its original name for compatibility: counts are security guidelines provided to each user (cached reminders included), not prevented-risk events.
Examples
query GetRisksPreventedByUser($input: VibeSecRisksPreventedByUserInput) {
getRisksPreventedByUser(input: $input) {
user
critical
high
medium
low
info
total
}
}Variables
This is an example input showing all available input fields. Only fields marked as required in the schema are mandatory.
{
"input": {
"dateRange": {
"from": 1749000000000,
"to": 1749900000000
},
"limit": 10
}
}Arguments
You can use the following argument(s) to customize your getRisksPreventedByUser query.
Optional date range and max number of users
dateRange VibeSecDateRange
limit Int
Fields
Return type: [VibeSecRisksPreventedByUserItem!]!
You can use the following field(s) to specify what information your getRisksPreventedByUser query will return. Please note that some fields may have their own subfields.
user String!
Developer username
critical Int!
Security guidelines with Critical severity provided to the user
high Int!
Security guidelines with High severity provided to the user
medium Int!
Security guidelines with Medium severity provided to the user
low Int!
Security guidelines with Low severity provided to the user
info Int!
Security guidelines with Info severity provided to the user
total Int!
All security guidelines provided to the user, including any with an unrecognized severity
Last updated