latio 1.2.7

Latio Application Security Tester - Uses OpenAPI to scan for security issues in code changes

Latio Application Security Tester

Use OpenAI or Gemini to scan your code for security and health issues from the CLI. Bring your own tokens. Options to scan full code, code changes, or in pipeline. Now with AI agents for deeper analysis and automated fixes.

About Latio
Find Security Tools

• Install
• How to Run Locally
• How to Run in Pipeline
• Command Line Options

Install

pip install latio

export OPENAI_API_KEY=xxx

latio partial-agentic ./ 

partial-agentic should be used on a new branch full-agentic can be used on an existing code base

How to Run Locally

1. Get your OpenAI key from here, and/or your Google API key here
2. export OPENAI_API_KEY=<OpenAPI Key> and/or export GEMINI_API_KEY=<Gemini API Key>
3. Scan only your changed files before merging with latio partial /path/to/directory. This uses the gpt-4o model by default. For Google, use python latio partial /path/to/directory --model=gemini-pro
4. Scan your full application with latio full /path/to/directory. This uses gpt-4o by default. Due to the context window, you may need to pass specific folders. For google, use latio full /path/to/directory --model=gemini-pro
5. Use the agentic analysis with latio partial-agentic or latio full-agentic for deeper code understanding and automated fixes
6. You can specify --model with the model name from open ai to experiment

Known Issues

1. Haven't tested gemini for 2.5
2. github workflows currently don't work, but should be switched over to the agentic model

How to Run in Pipeline

Functionality currently busted

This will run OpenAI in pipeline against only your changed files. Here's an example of what it looks like, it uses GPT-3.5 to scan only changed files, so it's relatively cheap.

1. Get your OpenAI token from here
2. In your repository, go to github.com/org/repo/settings/secrets/actions and add a new Repository Secret called OPENAI_API_KEY with the value from OpenAI
3. Copy and paste the .github/workflows/actions-template-security.yml (or -health for health scan) into your own .github/workflows/ folder.

Command Line Options

latio partial <directory> [--model <model_name>] [--health]

Scans only the files that have been changed in the specified directory.

• <directory>: Path to the directory where your project is located.
• --model <model_name>: (Optional) Specifies the name of the OpenAI model to use for the scan. Defaults to gpt-4o
• --health: (Optional) Runs a prompt focused on code optimization

Example:

latio partial /path/to/your/project --model gpt-4o --health

latio partial-agentic <directory> [--model <model_name>] [--health]

Scans only the files that have been changed in the specified directory using AI agents for deeper analysis.

• <directory>: Path to the directory where your project is located.
• --model <model_name>: (Optional) Specifies the name of the OpenAI model to use for the scan. Defaults to gpt-4o
• --health: (Optional) Runs a prompt focused on code optimization

Example:

latio partial-agentic /path/to/your/project --model gpt-4o --health

latio full <directory> [--model <model_name>] [--health]

Scans your entire codebase for security and health issues.

• <directory>: Path to the directory where your project is located.
• --model <model_name>: (Optional) Specifies the name of the OpenAI model to use for the scan. Defaults to gpt-4o
• --health: (Optional) Runs a prompt focused on code optimization

Example:

latio full /path/to/your/project --model gpt-4o --health

latio full-agentic <directory> [--model <model_name>] [--health]

Scans your entire codebase using AI agents for deeper analysis and automated fixes.

• <directory>: Path to the directory where your project is located.
• --model <model_name>: (Optional) Specifies the name of the OpenAI model to use for the scan. Defaults to gpt-4o
• --health: (Optional) Runs a prompt focused on code optimization

Example:

latio full-agentic /path/to/your/project --model gpt-4o --health