This is especially important if it is a fork; forks should be able to reasonably keep up with updates from upstream. However, many forks frequently fall behind and leave users exposed to vulnerabilities that may have been patched by the upstream. Regardless of security hardening/privacy features a browser has, it should stay on top of security updates.
Would need a system to determine how frequently (at least on average/median) a browser is updated... could probably be some type of point system to "rank" it. May need to fetch versioning automatically, as opposed to checking by hand - just an idea, would take some time to implement.
For browsers that are the upstream, could probably just indicate that. Otherwise, we would get into vulnerability management versus update frequency (in my opinion).
This is especially important if it is a fork; forks should be able to reasonably keep up with updates from upstream. However, many forks frequently fall behind and leave users exposed to vulnerabilities that may have been patched by the upstream. Regardless of security hardening/privacy features a browser has, it should stay on top of security updates.
Would need a system to determine how frequently (at least on average/median) a browser is updated... could probably be some type of point system to "rank" it. May need to fetch versioning automatically, as opposed to checking by hand - just an idea, would take some time to implement.
For browsers that are the upstream, could probably just indicate that. Otherwise, we would get into vulnerability management versus update frequency (in my opinion).