The ultralytics/source-trace
repository is a specialized tool designed to analyze and report code duplication between different Git repositories. This project extends the principles of the standard Ultralytics Python project template by focusing on code integrity and tracking. It helps developers identify potentially copied code segments across repositories, providing detailed insights into the source, destination, and metadata associated with each duplication instance.
- Detailed Comparison: Generates a detailed report of lines of code from one repository found in another.
- Comprehensive Statistics: Provides statistics about the extent of code duplication, including metrics by file and author.
- Metadata Tracking: Each instance of duplication includes metadata like the author and the date of the commit.
To start using source-trace
:
- Clone this Repository: Clone
source-trace
to your local machine or server. - Install Dependencies: Run
pip install -r requirements.txt
to install required Python packages. - Set Up Your Analysis: Follow the documentation in the
docs/
directory to configure your comparison setup. - Run the Tool: Execute the scripts in the
src/
directory to begin the analysis.
Ultralytics thrives on community collaboration; we immensely value your involvement! We urge you to peruse our Contributing Guide for detailed insights on how you can participate. Don't forget to share your feedback with us by contributing to our Survey. A heartfelt thank you ๐ goes out to everyone who has already contributed!
Ultralytics presents two distinct licensing paths to accommodate a variety of scenarios:
- AGPL-3.0 License: This official OSI-approved open-source license is perfectly aligned with the goals of students, enthusiasts, and researchers who believe in the virtues of open collaboration and shared wisdom. Details are available in the LICENSE document.
- Enterprise License: Tailored for commercial deployment, this license authorizes the unfettered integration of Ultralytics software and AI models within commercial goods and services, without the copyleft stipulations of AGPL-3.0. Should your use case demand an enterprise solution, direct your inquiries to Ultralytics Licensing.
For bugs or feature suggestions pertaining to Ultralytics, please lodge an issue via GitHub Issues. You're also invited to participate in our Discord community to engage in discussions and seek advice!