Submit a Repository
Submit a Git repository for analysis to identify security vulnerabilities and code quality issues.
Prerequisites
Before you can submit a repository, you need:
- Access to a Git repository (GitHub, GitLab, Bitbucket, or any Git-compatible URL)
- The repository URL (HTTPS format recommended)
Submitting a Repository
Step 1: Navigate to the Submit Page
- Log in to your account at https://app.canirunthat.com
- Click the Submit Repository button in the top navigation bar
Step 2: Enter the Repository URL
-
On the Submit Repository page, enter the HTTPS URL of your repository
- Example:
https://github.com/octocat/Hello-World - Example:
https://gitlab.com/username/project - Note: The
.gitextension is optional
- Example:
-
Once a valid Git repository is detected, you'll be prompted to select a branch
Step 3: Select a Branch
- Select the branch you want to analyze from the dropdown menu
- By default, the system selects "main"
- If "main" doesn't exist, it automatically tries "master"
- You can select any other available branch
Step 4: Configure Scheduled Rescans (Optional)
On the same form, you can optionally enable scheduled rescans:
- Toggle "Schedule recurring re-scans" on
- Choose the frequency:
- Weekly
- Monthly
- Quarterly
- Every 6 Months
- Annually
- Enter recipient email addresses (alerts will be sent when the repository's grade changes)
Step 5: Start Analysis
Click "Start Analysis" to submit the repository for analysis.
For sensitive, non-public codebases, Advanced options includes an opt-in setting to remove repository-unique file results after the report is safely generated. This is off by default and is not recommended for most repositories because retained results support later review and reduce future scan costs. See File Result Retention.
What Happens After Submission
After submission, you'll be taken to a status page showing the analysis progress.
Important: The status page may appear to freeze or hang while waiting for batch AI queries to complete. Processing can take anywhere from a few minutes to several hours. This is normal and expected — the system is processing your repository in the background.
Processing Time:
- The system uses batch processing with Anthropic for cost efficiency
- Processing can technically take up to 24 hours
- In most cases, analysis completes within a few minutes
Once complete, you'll be able to access the full report.
Viewing Your Report
To view your analysis report:
- From the Dashboard, find your repository in the list
- If the repository is still analyzing, you'll be on the status page
- Once complete, click on the repository to view the full security report
Alternative Submission Methods
- Browser Extension — See Submit a Browser Extension to analyze extensions from Chrome, Edge, or Firefox webstores
- NPM Package — To analyze a package from npmjs.com, see Submit an NPM Package
Next Steps
- Monitor Progress: Watch your repository analysis on the Repository Status page
- View Reports: Once analysis is complete, review your security findings in the Security Reports
- Schedule Scans: Set up automated scans in Scan Scheduling
Troubleshooting
Common Issues
"Repository not found" or "Access denied"
- Ensure the repository URL is correct and publicly accessible
- Try the HTTPS URL format
"Invalid repository format"
- Verify the URL uses HTTPS protocol (
https://) - Ensure it's a valid Git repository URL
"Branch not found"
- Confirm the selected branch exists in the repository
- Try submitting with the default branch first
Analysis could not be queued or remains pending
- Retry the repository from the dashboard; a failed queue setup does not start code analysis
- Pending Git repository submissions are checked automatically for recovery
- If the repository remains pending for more than 15 minutes, contact support with the repository name and approximate submission time
For additional help, contact support at Support.