[carlsverre]

No problem. :)

Possibly yes! If I had a project running in production with a team this seems very valuable as another layer of defense. With these kinds of scanning tools however, they are quickly ignored if they tend to emit noise. If at all possible (from a cost perspective) I'd focus on launching a free version for open source projects complete with a badge to add to the readme. Similar to other Linting/CI projects. Might help gain a bunch of traction in the short term, and if it's free folks may be likely to add it and leave it even if the accuracy isn't perfect which may be nice marketing for y'all.

[carlsverre]

Also... can you expand this to comments? Doesn't seem too different from logs. And then add in the fairly obvious auto-PR logic with the ability to respond to PR comments and now you're eliminating maintenance burden. Caveat: I dunno if anyone else is doing this, but this seems like a promising step.

[benjaminfh]

We're thinking alike. While we're iterating with customers, we're also thinking about how we can use it to contribute beneficially to projects (and in doing so prove it works reliably). One thing we are keeping a list of is popular OSS repos with notoriously spammy logs - if you know any, please let us know! We are planning to start with some of our YC batch mates' OSS projects once we get the quality right. I won't say exactly when we started showing the "fixes" but it was _very_ recently. Ensuring accuracy on identifying exceptions to the rules (aka the appropriate statements to touch in the first place) is the first thing we are perfecting.

We could expand to comments. The code maintenance direction is a possibility but the reason we get out of bed right now is to make a worthy contribution to logging -> debugging -> SRE sleep :)