Re:GitHub Codescanning
by lonelappde on Wednesday May 06, 2020 @01:57PM
(#23094219)
That's a problem that's simple to solve by putting a quota on # analyses per project per month, perhaps weighted by how popular the project is.
Like everything else at GitHub, private project users pay extra to cover the public project users. It's proportionall regardless of a feature's cost.
[ Parent
| on HN ]
Re:GitHub Codescanning
by marceloabsousa on Wednesday May 06, 2020 @02:03PM
(#23094284)
Not sure if that's simple - the cost of running a static analyser is almost never linear. For large popular projects, special care will have to be in place to make sure the analysis terminates and gives meaningful results (a basic timeout won't cut it...). I've experienced many times huge differences in the running times of analysers by minor changes in the code. It'll be interesting to see :-)