Interlynk
Platform Docs
Platform Docs
  • 👋Getting Started
  • Overview
    • ✨Interlynk Features
    • 🧭Navigating Dashboard
  • Product Guides
    • Interlynk Basics
      • Product
      • Version
      • SBOM
        • General
        • Parts
        • Component
        • License
        • Support
      • Vulnerability
      • Policy
      • Compliance
    • Managing Product
    • Importing SBOM
      • SBOM Checks
      • Automation Rules
      • Internal Components
      • Vulnerability Scan
    • Building SBOM
    • Managing SBOM
      • Editing General
      • Updating Components
      • Disposing Vulnerabilities
      • Evaluating Compliance
    • Distributing SBOM
    • Requesting SBOM
    • Monitoring Risks
    • Managing Policy
    • Inventorying Licenses
    • Auditing Changes
    • Managing Notifications
  • Administration
    • Getting Set Up
    • Inviting Users
    • Managing Roles
    • Setting Integrations
  • Use Cases
    • For Management
    • For Security Engineers
    • For OSPO Engineers
  • SUPPORT
    • Technical Support
    • Release Notes
Powered by GitBook
On this page
  1. Product Guides
  2. Interlynk Basics

Version

A version represents a specific product design, build, assembly, or release in a given environment.

Version and SBOM

Interlynk supports versioning as early as the product's design phase and can programmatically capture changes to the version using SBOM.

Interlynk supports one Version with multiple SBOMs associated with it.

This happens when the first SBOM associated with the version is modified to add details or fix errors, resulting in an updated SBOM that is later imported.

However, only one of those SBOMs is always considered to represent the version (the "active SBOM").

PreviousProductNextSBOM

Last updated 6 months ago