Fork of FloTorch is an open-source tool for optimizing Generative AI workloads on AWS. It automates RAG proof-of-concept development with features like hyperparameter tuning, vector database optimization, and LLM integration. FloTorch streamlines experimentation, ensures security, and accelerates production with cost-efficient, validated workflows.
active 2024-12-18 → 2025-10-08 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 295 days from 2024-12-18 to 2025-10-08. Pushes: 277 total, peak 21 in a day. Pull requests: 598 total, peak 48 in a day. Issues: 38 total, peak 9 in a day. Comments: 81 total, peak 11 in a day. Stars: 311 total, peak 40 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| nandateja | 563 | 199 | 245 | 36 |
| BalaSriharsha-Ch | 167 | 50 | 95 | 1 |
| dandamudigirish | 119 | 27 | 49 | 11 |
| harishFL | 62 | 0 | 56 | 6 |
| kgeorge-fission | 55 | 0 | 45 | 5 |
| abdul-fission | 51 | 0 | 45 | 4 |
| adilraza-fission | 39 | 0 | 29 | 1 |
| AkhilaTestAutomation | 30 | 0 | 1 | 4 |
| GMKR | 22 | 0 | 0 | 3 |
| prem-fissionhq | 14 | 0 | 4 | 4 |
| shailajafissionqa | 13 | 0 | 0 | 3 |
| rohandeshpande-sudo | 7 | 0 | 7 | 0 |
| shivakrishnaah | 6 | 0 | 5 | 0 |
| Ravifission | 5 | 0 | 4 | 1 |
| srujansirikonda1 | 4 | 0 | 4 | 0 |
| shivani-fission | 4 | 0 | 2 | 1 |
| lkumar009 | 4 | 0 | 4 | 0 |
| balualways | 3 | 0 | 1 | 1 |
| SohaibKatariwala | 2 | 0 | 0 | 0 |
| amazon-codecatalyst[bot] | 1 | 1 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Pull request#386rohandeshpande-sudo2025-09-30 04:59
- Pull request#384rohandeshpande-sudo2025-09-30 04:57
- Pull request#381rohandeshpande-sudo2025-09-30 04:54
- Pull request#380rohandeshpande-sudo2025-09-30 04:52
- Pull request#379rohandeshpande-sudo2025-09-30 04:50
- Pull request#375rohandeshpande-sudo2025-09-29 06:02
- Pull request#375rohandeshpande-sudo2025-09-28 20:45
- Pull request#374srujansirikonda12025-09-25 15:33
- Pull request#372srujansirikonda12025-09-18 15:59
- Pull request#371srujansirikonda12025-07-02 10:10
- Issue comment#366BalaSriharsha-Ch2025-06-19 15:52Login to Auto Clean Up S3 Data on CFN Stack Rollback or Deletion
- Pull request#366BalaSriharsha-Ch2025-06-19 15:52
- Pull request#369harishFL2025-06-11 12:08
- Pull request#367BalaSriharsha-Ch2025-06-06 07:27
- Pull request#367kgeorge-fission2025-06-04 11:30
- Pull request#364BalaSriharsha-Ch2025-05-23 17:53
- Pull request#355nandateja2025-05-21 10:23
- Pull request#365BalaSriharsha-Ch2025-05-20 11:48
- Pull request#365kgeorge-fission2025-05-20 11:40
- Issue comment#356balualways2025-05-13 21:47[Bug]: DataBucket name need to be unique. flotorch-data-(TableSuffix) results in duplicate Bucket names and stack failure
- Pull request#364balualways2025-05-13 21:46
- Issue#363AkhilaTestAutomation2025-05-13 11:01[Bug]: Experiments not generated when Guardrail option is set to "None"
- Issue#361AkhilaTestAutomation2025-05-13 08:41[Bug]: Some experiments fail during execution when guardrails are enabled.
- Issue#360AkhilaTestAutomation2025-05-13 08:38[Bug]: Input and Output token values are displayed as zero in the Cost Breakdown section.
- Issue#358AkhilaTestAutomation2025-05-13 08:20[Bug]: Evaluation metrics are showing as NaN (Not a Number) values after running an experiment, even though the experiment completes successfully.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 311 stars here means stars gained during the window, not the repo's star count.