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
{{ message }}
Repository navigation
Possible additional categories of secrets for rule codeguard-1-hardcoded-credentials #78
@billbrietstout, thanks for outlining these cases. Would this scope sound right?
Identify a coherent set of gaps in the current secret-handling guidance.
Update the relevant rules, examples, or documentation.
Keep the guidance model- and tool-agnostic. Where detection is needed, point users to purpose-built secret-scanning tools rather than expanding CodeGuard into a scanner.
Explain the selected gaps, provide representative secure guidance and examples, keep generated artifacts consistent, and pass repository validation.
This would exclude building a comprehensive secret scanner or maintaining an exhaustive catalog of provider-specific patterns.
Were any of the listed gaps based on specific CodeGuard results or examples that we should use as acceptance cases? If you would like to take this on, I can assign the issue to you.
Thanks again for raising these gaps and offering to help. PR #102 documents the proposed boundary: CodeGuard focuses on secure guidance, while dedicated scanners handle comprehensive detection. A few concrete CodeGuard examples would help turn this into focused rule or documentation work.
Activity
thomas-bartlett commentedon Jul 6, 2026
@billbrietstout, thanks for outlining these cases. Would this scope sound right?
This would exclude building a comprehensive secret scanner or maintaining an exhaustive catalog of provider-specific patterns.
Were any of the listed gaps based on specific CodeGuard results or examples that we should use as acceptance cases? If you would like to take this on, I can assign the issue to you.
billbrietstout commentedon Jul 6, 2026
Yes the scope sums it up. I was too specific, I looked at existing roles and saw a few secrets categories were not included.
Let me know where I can add value.
thomas-bartlett commentedon Jul 14, 2026
Thanks again for raising these gaps and offering to help. PR #102 documents the proposed boundary: CodeGuard focuses on secure guidance, while dedicated scanners handle comprehensive detection. A few concrete CodeGuard examples would help turn this into focused rule or documentation work.