⚡Megatron LLM Hub
←返回搜索
Twitter

记录漏洞位置应从文件名和行号改为 commit hash 加代码快照

报告
Remember: the codebase you're reviewing is alive, and it won't stop changing just because you're taking notes. When documenting a potential vulnerability, don't record only the filename and line number. Code moves, code changes, files get renamed, and your reference might point to something completely different by the time someone reads your findings. Always keep the filename, line number, commit hash, and a copy of the relevant code, along with an explanation of the issue. If you include a link, make sure it points to that specific commit, not to the branch. Your notes should still make sense after the code has changed.