Audit public gists for internal APIs and sensitive information

Audit public gists for a given repo for non-public APIs or sensitive information exposed. We can use some off-the-shelf secrets scanner for this but it might be trickier to automatically detect snippets. We can definitely provide awareness for users' activity though by outlining their public gists

No files, tests, or entry points are named. Start by reviewing the repository's existing GitHub audit flow, then define how public gists for a repository are found and what counts as an exposed internal API or sensitive value; done should include a documented scope and reliable reporting behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.