Others have gotten into how OSM fights vandalism, but I can tell you a little about what it is like to consume the data. About a decade ago I was in the public

Others have gotten into how OSM fights vandalism, but I can tell you a little about what it is like to consume the data. About a decade ago I was in the public sector and we wanted to switch from google maps to OSM in our route calculation tool for the Danish travel-to-work tax deduction (translated). Initially we didn't change how the app worked, so we paid some organisation for an api access which worked similar to how a google maps api work. After a year or so we eventually rebuild the engine to keep a local copy of OSM where we had our GIS team do incremental and reviewed updates. This was not because of vandalism, but because of how hard it was to update OSM when you don't do it often and might not look trustworthy. In Danish cities we have a complicated relationship with cars, we don't want them, but we do want the people they bring. One of the obstacles we create is having a lot of one way streets, and when OSM gets an error on those... well... suddenly there is a lot of addresses you simply can't reach. I once updated one of these errors with a photo from the internet, and it was rejected after a few miniutes because I had used an image from the internet which is (was?) against the TOS. Unfortunately the company we bought the API from was not doing any form of validation, so we had a week where our 5000 employess couldn't registerer driving to the most commonly used adress in the neighbouring city. I posted all sorts of documentation proving my official function, and had a discussion with the admins and even though they agreed I was right they refused to let me correct the mistake without real evidence. So eventually I drove my bicycle the 50km to the location, took some pictures and a couple with silly hats and submitted them and got my correction. Once we had a local copy of the danish map we had no issues. I assume you would do this for any app relying on working routing data.