GitHub Actions
GitHub Actions
Use these steps if your repositories are on GitHub.com or GitHub Enterprise Cloud. The scan runs on a GitHub-hosted runner and connects to the Lineaje SaaS MCP endpoint.
Choose an MCP Server configuration
Choose the MCP Server configuration for this workflow.
Lineaje-hosted MCP Server
Use the existing Lineaje SaaS MCP endpoint configuration below.
https://mcp-code.v2.prod.veedna.com/mcpCustomer-hosted Hybrid MCP Server
Configure the workflow to use your Hybrid UnifAI MCP Server endpoint:
https://<CUSTOMER_VM_OR_FQDN>/mcpBefore configuring this option:
The Hybrid UnifAI MCP Server must already be deployed.
The MCP Server health check must succeed.
The GitHub Actions runner must be able to reach the configured MCP endpoint.
Deploy and verify the server first in Deploy UnifAI on Azure.
Lineaje-hosted MCP Server
Before You Start
A GitHub.com account, with permission to add repository or organization secrets and to enable GitHub Actions.
A Lineaje PAT (Personal Access Token).
Generate a Lineaje PAT
A Lineaje PAT authenticates the GitHub Action to Lineaje.
Follow these steps to generate a Lineaje PAT from your Lineaje account. The token grants the Action access to the Lineaje scan service:
Log in at app.veedna.com and navigate to SBOM360 → Integrations → Deploy Private Cloud → Personal Access Token.
Click the link in the box.
Click Generate Token. A Lineaje login webpage opens.
Authenticate and click Yes. You are returned to the Integrations page.
Copy the PAT displayed on the Integrations page.
Add the Lineaje PAT to Your GitHub Repository or Organization
Store the Lineaje PAT as an encrypted secret so the GitHub Action can read it at runtime.
In GitHub, go to your repository (or organization) Settings → Secrets and variables → Actions.
Click New repository secret (or New organization secret). The secret form opens.
In the Name field, enter
LINEAJE_PAT_TOKEN.In the Secret field, paste the Lineaje PAT from Step 1. Click Add secret. The secret appears in the list, masked.
Use default GITHUB_TOKEN or generate custom token
By default, the GitHub Actions workflow authenticates using GITHUB_TOKEN. The sample GitHub Actions workflow below uses the default token.
Depending on the repository settings or organization settings, you might have to enable GitHub Actions to create Pull Requests.
Alternatively, use a personal access token, create a token and replace secrets.GITHUB_TOKEN with your token name.
Copy GitHub Actions workflow file to central repository
Copy the below script and place it in a new file in the central repository under the .github/workflows folder. This file can be named lineaje-unifai-scan.yaml.
The on: events can be modified to trigger off new commits, new pull requests, etc. In the following example, the workflow is configured to run manually.
Last updated