Name: Is this GitHub repo actually being scanned, or just quiet
Author: recued-core

Is this GitHub repo actually being scanned, or just quiet

by recued-core v1 8 views

Use “Is this GitHub repo actually being scanned, or just quiet” in Recued. The same alert list is wrong in both directions. It reads information without changing data in the connected service.

How it works 32 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (32 steps)

■ setup_raw ?

■ scanning_state default

Apply default

■ scanning_configured compare

Check if scanning state equals configured

■ scanning_off compare

Check if scanning state equals not-configured

■ defaults defaults

Apply defaults

■ code_raw ?

■ code_alerts default

Apply default

■ dep_raw ?

■ dep_alerts default

Apply default

■ anything_known any

Check if any of the conditions are true

■ have_signal template

Generate text from a template

fail: step.anything_known equal false

■ code_total count

Count items in code alerts

■ code_open filter

Filter by condition

■ code_open_count count

Count items in code open

■ code_dismissed filter

Filter by condition

■ code_dismissed_count count

Count items in code dismissed

■ code_fixed filter

Filter by condition

■ code_fixed_count count

Count items in code fixed

■ dep_total count

Count items in dep alerts

■ dep_open filter

Filter by condition

■ dep_open_count count

Count items in dep open

■ dep_auto_dismissed filter

Filter by condition

■ dep_auto_dismissed_count count

Count items in dep auto dismissed

■ dep_closed filter

Filter by condition

■ dep_closed_count count

Count items in dep closed

■ dep_critical filter

Filter by condition

■ dep_critical_count count

Count items in dep critical

■ code_page_full compare

Check if code total is at least 100

■ dep_page_full compare

Check if dep total is at least 100

■ card to_summary

Format results as a summary card

■ open_code_table to_table

Format results as a data table

■ open_dep_table to_table

Format results as a data table

Settings 3 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

repo setting = [object Object]

owner setting = [object Object]

github setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Read your Github connection

Declared by the recipe — Recued grants these at install, where you review them before approving.

About

recued-core

Details

32 steps 3 configurable settings recipe_id: review-scan-coverage-github

Is this GitHub repo actually being scanned, or just quiet

Trust & control

Permissions it requires

About

Tags

Details