What you can do in the RunSafe Security Platform

Sign in at app.runsafesecurity.com to generate and manage Software Bill Of Materials (SBOMs), identify vulnerabilities, enforce license and vulnerability policy, and more.

Most teams can do this from the Platform alone. Use the Identify and Protect docs when you need to integrate manually.

Common tasks

Generate SBOMs

Task	When to use it
Connect GitLab	Your code is on GitLab.com or self-managed GitLab and you want SBOMs from GitLab CI.
Connect GitHub	Your code is on GitHub.com and you want SBOMs from GitHub Actions.
Connect GitHub Enterprise	Your code lives on a self-hosted GitHub instance.
Build with Jenkins	A GitHub or GitLab repo is already connected, but the pipeline that builds it runs on Jenkins.
Connect without CI	You have no GitHub or GitLab repo—vendor software, offline builds, or SBOM files to upload.

Manage Your SBOMs

Task	When to use it
Review Builds	You need Build history, Build Comparison, or reports for a non-default-branch commit.
Review an SBOM report	You need component inventory, dependency relationships, download a report, or retry a failed scan.
Find a component across projects	You need to see which projects use a name and version.
Find and triage vulnerabilities	You need to decide what to fix first across projects or on one Build.
Review license findings	You need to see which licenses conflict with your policy.
See Protect coverage and enable Protect	You want to know which projects mitigate memory-safety issues, or turn Protect on.
Run a risk reduction analysis	You want to analyze a binary together with its SBOM.

Enforce License and Vulnerability Policy

Task	When to use it
Fail builds on vulnerability thresholds	You want GitHub or GitLab checks to fail when critical, high, or known-exploited findings appear.
Set license policy	You need organization defaults, or different rules per project.
Get email alerts for new vulnerabilities	You want a summary when automated scans find new critical, high, or known-exploited issues.

Manage Your Organization

Task	When to use it
Create an account and your first organization	You are new to the Platform or need a new organization.
Accept an organization invite	Someone invited you and you need to join their organization.
Switch between organizations	Your account belongs to more than one organization and you need to change the active organization.
Invite teammates	Someone needs access to this organization.
Let members sign in with SSO	You want organization members to use your identity provider.
Use your license key	You are configuring Identify or Protect outside the Platform.
Manage your account	You need to change your profile or reset a password.

Terms you will see

Term	Meaning
Organization	A workspace in the Platform. Your account can belong to more than one organization; members, settings, connected repositories, and Generic projects belong to whichever organization is active.
Project	An SCM-backed repository connection, or a Generic project you manage by uploading SBOMs.
Builds	An analyzed CI pipeline run for an SCM-backed project. Project SBOMs, Vulnerabilities, and License compliance summarize the latest complete Build on the default branch; open Builds for history. Generic projects use uploaded SBOM data instead.