Mikail Tunç

I tested your PR and it found the examples you gave but missed other test ones in my test Slack channels. More work to be done here to improve the...

Thanks for the PR @kmmanoj - apologies it's taken this long to actually look at it. I'm going to see if I can further improve this as it wasn't catching...

Definitely in favour of this - proxying is a pain atm and it's definitely needed for testing purposes! Will see what we can conjure up :)

Slack tokens - look for Slack tokens that may have been leaked within a Slack Workspace. This could allow an attacker to pivot to a more privileged user or someone...

Github tokens - unless there's a unique way to differentiate these from other 40 character strings then this might introduce some false positives. Worth a try though.

Azure secret keys

Google Cloud Platform secret keys

Password and/or tokens in URLs

> API Reference for listing pinned items: https://api.slack.com/methods/pins.list > > May also require listing channels (https://api.slack.com/methods/channels.list) as the channel with the pinned items must be specified This has been implemented...

I've run into this too - I wonder if the script is running into a pagination issue of some sort.