What inputs does the Vulnerability Scanner workflow use?

The workflow uses Dependencies. Required fields and their expected formats are listed on this page.

What resources are included in the Vulnerability Scanner blueprint?

The blueprint contains 2 AI agents, 0 functions, 0 MCP servers. Its workflow pattern is Dag.

All blueprints Engineering AI workflow blueprint

AI Vulnerability Scanner workflow blueprint

Scan your dependency list, check for known vulnerabilities, and get a prioritized fix plan

See where this blueprint fits in the production workflow lifecycle

Engineering

Security

Dependencies

Vulnerability

Request access

Pattern

Dag

Agents

2

Functions

0

MCP servers

0

Inputs for the Vulnerability Scanner workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

Dependencies
Required
Dependency list (package.json, requirements.txt, etc.)
Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "dependencies": "<required string>"
}

How the Vulnerability Scanner AI workflow works

This engineering blueprint uses a dag workflow with 2 agents, 0 functions, and 0 MCP servers. This catalog blueprint is available by request; contact GraphN to discuss access and customization for your use case.

Dependency Scanner
Agent using Dependency Scanner
Remediation Planner
Agent using Remediation Planner

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

AI agent

Dependency Scanner

Scan the dependency list for known CVEs, outdated packages, and security advisories.

AI agent

Remediation Planner

Create a prioritized fix plan with severity ratings, upgrade paths, and breaking change warnings.

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients:

Planner

Frequently asked questions

What does the Vulnerability Scanner blueprint do?: Scan your dependency list, check for known vulnerabilities, and get a prioritized fix plan
What inputs does the Vulnerability Scanner workflow use?: The workflow uses Dependencies. Required fields and their expected formats are listed on this page.
What resources are included in the Vulnerability Scanner blueprint?: The blueprint contains 2 AI agents, 0 functions, 0 MCP servers. Its workflow pattern is Dag.
Can I customize the Vulnerability Scanner blueprint in GraphN?: This blueprint is currently available by request. Contact GraphN to discuss access and customization for your use case.

Related Engineering blueprints

View all software engineering workflows

API Data Summarizer

Fetch any public JSON API and get a clear, plain-language summary of the response

API Docs Generator

Point it at your API code and get OpenAPI-style docs with examples

Architecture Decision Record Writer

Describe a technical decision, get a formatted ADR with tradeoffs and alternatives

Production Incident Response

Triage a production incident: analyze the alert, logs, and evidence in parallel and propose next steps