offline cloned repository scanning · Issue #22 · techgaun/github-dorks · GitHub
Skip to content

offline cloned repository scanning #22

Closed
#72
Closed
offline cloned repository scanning#22
#72
Labels
enhancement

Description

@techgaun
techgaun
opened on Mar 3, 2017

the way it would work is run github-dorks as an offline tool and use regex and text patterns to find potential leaks.. optionally see if we can also scan history

Activity

  1. Plazmaz commented on Mar 3, 2017

    @Plazmaz
    Plazmaz
    on Mar 3, 2017
    Collaborator

    I like the idea of setting up a pre-commit hook.

  2. Plazmaz commented on Jul 20, 2017

    @Plazmaz
    Plazmaz
    on Jul 20, 2017
    Collaborator

    Actionable steps to achieve this:

    1. Clone repo. I suggest using GitPython or similar for git management.
    2. Write system for parsing GitHub search syntax, similar to https://github.com/Plazmaz/GHScraper/blob/master/index.js#L16-L33 and https://github.com/Plazmaz/GHScraper/blob/master/index.js#L89-L113 (sorry, messy)
    3. Convert dorks into objects
    4. Iterate commit diffs via GitPython and check them against the objects
  3. Plazmaz
    added
    enhancement
    on Jul 27, 2017
  4. techgaun
    closed this as completedin #72on Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions