感谢佬开源。感觉文件后缀名提取这些可以写个公共配置

Nobody has claimed this yet.

今天运行了一下前端项目(vue)，发现很多分析出来的风险死活拿不到行号和file_path，看了下代码发现现在还是挺多硬编码文件后缀名的，比如
any(potential_file.endswith(ext) for ext in ['.py', '.js', '.ts', '.java', '.go', '.php', '.rb', '.c', '.cpp', '.h'])):

TEXT_EXTENSIONS = [
".js", ".ts", ".tsx", ".jsx", ".py", ".java", ".go", ".rs",
".cpp", ".c", ".h", ".cc", ".hh", ".cs", ".php", ".rb",
".kt", ".swift", ".sql", ".sh", ".json", ".yml", ".yaml"
]

r'.*auth.*\.(py|js|ts|tsx|jsx|java|php|swift|m|mm|kt|rs|go)$',

不过感觉这情况也不是很多哈哈哈，以框架命名后缀名的好像就只有包含vue的寥寥几个

No file or test is named. Search the codebase for the hard-coded endswith list, TEXT_EXTENSIONS, and the auth filename regex, then trace where they determine line numbers and file paths. Consolidate the extension sources into one shared configuration and rerun the frontend analysis described in the issue to confirm those results are populated.

Written by the indexing model from the issue text.