You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m a master’s student researching cost considerations in cloud infrastructure. As part of this project, we ran a static analysis tool (linter) on your repository to identify cost-related misconfigurations.
We found 56 potential issues across 51 files, some of which might significantly affect the cloud costs of your project.
Are you interested in the linter results? Reply here. We’ll send the report along with a short follow-up survey (~5 min) to evaluate our tool and better understand cost considerations in open-source projects for our research. All data will be treated confidentially.
If you’re curious about our work, we are investigating how developers approach cost in cloud infrastructure, specifically Terraform and AWS CloudFormation. Our goal is to identify patterns and anti-patterns to help developers make more cost-aware infrastructure decisions. You can check out what we’ve discovered so far here: https://search-rug.github.io/iac-cost-patterns/. If you have any questions or would like to discuss our research, don’t hesitate to reach out!
Thank you for your time and support! 🤗
Allia Neamt, MSc Student (Computing Science)
Faculty of Science and Engineering
Rijksuniversiteit, Groningen
Thank you for reaching out! I believe the linter results you found were for our tests for the SAM transform. We use these resources ephemerally as a way to test that things are working properly, and they're in place to find edge cases. I will be resolving this issue.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
Activity
reedham-aws commentedon May 13, 2026
Thank you for reaching out! I believe the linter results you found were for our tests for the SAM transform. We use these resources ephemerally as a way to test that things are working properly, and they're in place to find edge cases. I will be resolving this issue.
github-actions commentedon May 13, 2026
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.