npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@versio-io/n8n-nodes-versio-lifecycle-vulnerability-audit

v1.0.4

Published

n8n node for auditing lifecycle and security state using Versio.io

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

matthias.scholzematthias.scholzearyan.massoudyaryan.massoudyfabian.klosefabian.klose

Keywords

Lifecycle & Security CheckLifecycleMaintenanceSupportLTSLong term supportMajorMinorPatchEOLSecurityvulnerabilityvulnerability checkVersioioVersio.ion8n-community-node-package

Readme

Versio.io Lifecycle & Vulnerability Audit node for n8n

This is an n8n community node. It lets you use the Versio.io Product lifecycle & security API in your n8n workflows.

The Lifecycle & Vulnerability Audit node allows you to verify the version vulnerabilities, maintenance time-span, support, and security problems of your software and hardware products and technologies to ensure IT governance.

This node acts as a compliance gate, enabling enterprises to automate the checking of their deployed product versions against the Versio.io Product lifecycle & security API. It can be used within an automated workflow to process large inventories, trigger security alerts, and much more.

n8n is a fair-code licensed workflow automation platform.

Table of Content

Installation

Operations

Credentials

Compatibility

Usage

Resources

Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

Operations

The Versio.io Lifecycle & Vulnerability Audit node allows you to perform an audit on a specific product's vendor, name, and version to check its lifecycle, maintenance, support, and security status (including known CVEs) using the Versio.io Product lifecycle & security API.

Credentials

Before using the Versio.io Lifecycle & Vulnerability Audit node, you must have the following prerequisites:

  1. Product vendor, name and version.
  2. Versio.io API Token: A token for the Versio.io Product lifecycle & security API. This is the required credential for the node. You can request your token here.
  3. n8n instance: A running server instance of n8n.

Compatibility

This node has been developed and tested using n8n version 1.123.5.

Usage

Integrating Versio.io Lifecycle & Vulnerability Audit node into n8n Workflow

In order to add the Versio.io node into your n8n instance, go to your n8n workflow and either click on the plus sign next to your current node in the workflow or click on the open nodes panel button. In the search bar, search for Versio and you will see this node.

Node Usage: Versio.io Lifecycle & Vulnerability Audit

The node takes three mandatory input parameters to perform the audit:

| Display Name | Parameter Name | Type | Description | Example | | :--- | :--- | :--- | :--- | :--- | | Vendor | vendor | String | The name of the software vendor. Please see the exact name of the vendor here. | Apache | | Product | product | String | The name of the product. Please see the exact name of the product here.| Tomcat | | Version | version | String | The specific version string of the product. | 10.0.22 |

These parameters can be supplied by:

  • Static values entered directly into the node configuration.
  • Expressions pulling data from previous nodes (e.g., from an inventory list).

Once the node is run successfully, you will receive a JSON describing the specified product. It typically includes the following information:

  • Lifecycle: Indicates if a product version is a stable release, the latest release version, the latest release, or the latest long term support (LTS) release.
  • Maintenance & support: Check if maintenance and support is currently available for the used product version.
  • Security: Check if there are any known security vulnerabilities (CVEs) for the product version.
  • Recommended tasks: Describes specific update version information alongside the results, which will help you restore governance compliance in terms of lifecycle and security.

Setting Up Credentials

Before using the node in a workflow, you must set up the API Token as a credential in n8n.

  1. In your n8n instance, click "Credentials" in the sidebar.
  2. Click "Create Credential" and search for "Versio.io" (related to this node).
  3. You will be asked to enter the API Token.
  4. Upon saving, an automated test will be made. You will see an n8n green banner, indicating that the test for the API token has been successful. You can now use this credential across your Versio.io nodes.

Resources

Version history

Versio.io Lifecycle & Vulnerability Audit node version