Launch HN: Datree (YC W20) – Best practices and security policies on each commit
11–20 of 54 posts
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#12Why wouldn't someone just use github actions and token scanning. https://github.com/features/actions https://developer.github.com/partnerships/token-scanning/
- Identify the relevant tokens you want to scan for, and create regular expressions to capture them.
- Create a token alert service which accepts webhooks from GitHub that contain the token scanning message payload.
- Implement signature verification in your token alert service.
- Implement token revocation and user notification in your token alert service.
And that would replace one piece of what this does.
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#13So this sounds like git-hooks-as-a-service. Am I right in that assessment?
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#14Would you mind sharing an example of a custom rule?
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#15Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#16Why wouldn't someone just use github actions and token scanning. https://github.com/features/actions https://developer.github.com/partnerships/token-scanning/
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#17Wondering if there any open source project which does similar things? (surprised if it's not)
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#18From my experience it’s quite hard to monetize developer tools except maybe when focusing on security, so it’s good you seem to have that as a focus as well. Good luck!
Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit
#19Isn't it too late once it is committed to github? It seems like this would be much more useful as a service running as a precommit hook on each workstation. Probably harder to ship/monetize that but as far as actually solving the problem wouldn't that be better?