Skip to main content

​
Your First Analysis

This guide walks you through running your first code security analysis with Clipron AI. We’ll cover all the options and help you understand the results.

​
Before You Start

Make sure you have:
  • ✅ Created and verified your Clipron AI account
  • ✅ Logged into your dashboard
  • ✅ Have some code ready to analyze (repository, files, or snippets)

​
Starting a New Analysis

​
From Your Dashboard

1

Access Dashboard

Log into clipron.com and navigate to your main dashboard
2

Click New Analysis

Click the prominent “New Analysis” button in the center of your dashboard
3

Choose Analysis Method

Select how you want to provide your code for analysis

​
Code Input Methods

​
Method 1: GitHub Repository

Best for: Open source projects, public code
  1. Select “GitHub Repository” tab
  2. Enter the repository URL (e.g., https://github.com/user/repo)
  3. Choose branch (defaults to main/master)
  4. Select specific directories if needed
  5. Click “Load Repository”

​
Method 2: Direct Code Paste

Best for: Code snippets, specific functions, quick tests
1

Select Paste Code

Click the “Paste Code” tab in the analysis interface
2

Choose Language

Select your programming language from the dropdown for proper syntax highlighting
3

Paste Your Code

Copy and paste your code into the editor. The interface supports:
  • Syntax highlighting for 50+ languages
  • Line numbers for easy reference
  • Code folding for large snippets
4

Add Context (Optional)

Provide additional context about the code’s purpose or specific concerns

​
Method 3: File Upload

Best for: Local files, multiple files, compressed archives
  • Click “Choose File” button
  • Select your code file (supports most programming languages)
  • Maximum file size: 10MB
  • Supported formats: .py, .js, .java, .cpp, .cs, .php, .rb, .go, etc.
  • Use Ctrl/Cmd+Click to select multiple files
  • Or drag and drop multiple files into the upload area
  • Files are analyzed as a cohesive project
  • Upload ZIP, TAR, or RAR archives
  • Automatically extracts and analyzes all code files
  • Maintains directory structure for context
  • Maximum archive size: 50MB

​
Selecting Analysis Type

Choose the right analysis level for your needs:

Ron AI 2 Mini

Quick Scan
  • Cost: 2-5 credits
  • Time: 30-60 seconds
  • Model: Google Gemini Flash
  • Best for: CI/CD, quick checks

Ron AI 2 Standard

Comprehensive Audit
  • Cost: 5-15 credits
  • Time: 1-3 minutes
  • Model: DeepSeek Coder V2
  • Best for: Regular security audits

Ron AI 2 Ultra

Deep Analysis
  • Cost: 15-50 credits
  • Time: 3-10 minutes
  • Model: Claude 3.5 Sonnet
  • Best for: Pre-production, critical code

​
Choosing the Right Analysis Type

Recommended: Start with Ron AI 2 Mini
  • Low cost to experiment
  • Fast results
  • Good overview of major issues
  • Perfect for learning the platform

​
Analysis Configuration

​
Advanced Options

Specify what to prioritize:
  • Security vulnerabilities: SQL injection, XSS, etc.
  • Authentication issues: Login, session management
  • Data handling: Input validation, sanitization
  • Cryptography: Encryption, hashing, key management
Check against specific standards:
  • OWASP Top 10: Web application security
  • CWE: Common Weakness Enumeration
  • SANS Top 25: Most dangerous software errors
  • Custom rules: Your organization’s standards
Skip certain files or patterns:
  • Test files (usually safe to exclude)
  • Third-party libraries
  • Generated code
  • Documentation files

​
Running the Analysis

1

Review Settings

Double-check your code input, analysis type, and configuration options
2

Check Credit Cost

Review the estimated credit cost displayed at the bottom of the form
3

Start Analysis

Click “Start Security Analysis” to begin the process
4

Monitor Progress

Watch the progress bar and status updates as your code is analyzed

​
Understanding the Progress

During analysis, you’ll see:
  1. Preprocessing (10-20%): Code is parsed and prepared
  2. AI Analysis (20-80%): Ron Cortex engine examines your code
  3. Report Generation (80-100%): Results are compiled and formatted
Don’t close your browser during analysis. While the process continues server-side, you’ll need to refresh to see results.

​
What Happens Next

Once analysis completes:
  • Instant notification: Browser notification when ready
  • Email alert: Optional email with results summary
  • Dashboard update: Analysis appears in your history
  • Detailed report: Full security report with findings

​
Sample First Analysis

Here’s what a typical first analysis might look like: 
{
  "analysis_id": "first-analysis-123",
  "timestamp": "2024-06-18T10:30:00Z",
  "code_source": "paste",
  "analysis_type": "mini",
  "credits_used": 3,
  "security_score": 78,
  "total_issues": 5,
  "breakdown": {
    "critical": 0,
    "high": 1,
    "medium": 2,
    "low": 2
  },
  "top_issues": [
    {
      "type": "Input Validation",
      "severity": "high",
      "line": 42,
      "description": "User input not sanitized before database query"
    }
  ]
}

​
Next Steps After Your First Analysis

Review Results

Learn how to interpret your security report and findings

Fix Vulnerabilities

Step-by-step guides for fixing common security issues

Set Up Automation

Automate security analysis for your repositories

Explore API

Integrate Clipron AI into your development workflow

​
Tips for Better Results

Include context: Add comments explaining complex logic or business rules to help the AI understand your code better.
Start small: Begin with smaller code samples to understand how Clipron AI works before analyzing entire projects.
Regular analysis: Run security analysis regularly, not just before releases, to catch issues early.