Live data from Hacker News

Launch HN: Datree (YC W20) – Best practices and security policies on each commit

news.ycombinator.com

11–20 of 54 posts

Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit

#12

Why wouldn't someone just use github actions and token scanning. https://github.com/features/actions https://developer.github.com/partnerships/token-scanning/

For starters, that "just" is swallowing:

- 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

#13
post #5

So this sounds like git-hooks-as-a-service. Am I right in that assessment?

You might call it that in a way. This is where the engine is hooking. We scan the entire source control and curate rules for you to use around technologies

Re: Launch HN: Datree (YC W20) – Best practices and security policies on each commit

#18
Funny we built almost the same product 6 years ago (sold it to a competitor), we even did automated refactoring of Python code. We also developed a regex-like language that could operate on abstract syntax trees / annotated graphs, which we wrote all our checks with. We were working on extending that with a graph database backend and symbolic execution, basically building a large code graph that we would perform pattern matching on. We didn’t finish this work as we sold the company before that, in retrospect I often wonder what would have happened if we had kept developing it.

From 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

#19
>What we built is a rules engine, which is essentially a server-side git-hook platform.

Isn'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?

Post reply on HN