The FOSS server [[https://fossies.org|fossies.org]] - supporting also the [[https://fossies.org/linux/limesurvey|LimeSurvey]] project - offers among others a feature named "[[https://fossies.org/features.html#codespell|Source code misspelling reports]]". Such reports are normally only generated on request, but as Fossies administrator I have created for testing purposes such a [[https://github.com/codespell-project/codespell|codespell]] based analysis for the LimeSurvey GitHub "master" version:

https://fossies.org/linux/test/limesurvey-master.tar.gz/codespell.html

That version-independent URL should redirect always to the report for the latest "master" version identified by the short GitHub commit ID and a year-month-day string (YYMMDD) representing the according git pull date (mostly = commit date). The data are residing within a special restricted "test" folder that isn't really integrated into the standard Fossies services and should also not be accessible to search engines. The report should be available at least for some weeks and is continuously updated (currently with a half-hourly refresh rate).

By the way, the context type of the spelling errors and typos are marked by a single character (within the sortable column "T"): The less interesting, probably not user visible ones (in "comments") are greyed, while the probably more interesting ones are black-colored. Especially interesting may be unassigned errors marked by a "?" since they may be contained in the source code itself. Some more according information is offered by a tooltip if the mouse is over the string "error context type character" above the table, over the "T" in the table header or over such a context character itself within the table. If JavaScript is enabled all table columns are sortable.

Although after a first review some obviously wrong matches ("False Positives" = FPs) are already filtered out (ignored) please inform me if you find more of them so that I can exclude them if applicable.

Just for information there are also three supplemental pages showing some used "codespell" [[https://fossies.org/linux/wwwlimesurvey/codespell_conf.html|configuration details]], all obvious [[https://fossies.org/linux/www/limesurvey/codespell_fps.html|false positives]] and a [[https://fossies.org/linux/www/limesurvey/codespell_hist.html|misspelling history]] (log).

OK, spelling corrections certainly have a low priority, but they may also contribute to the overall quality of a software project. So I hope that the report can nevertheless be a little bit useful.