Week_8 & Week_9 : Coding period - Progress Report

Due to some urgent travel I was not able to update the Week_8 report, this report summarize what I did in both week.
Any latest code will be found in this repository : GitHub - akshajrawat/plugins-test · GitHub

What I did :

Firstly, I focused on running the codeql rule test on all of the 30 plugins listed in Joplin Plugins website. The tests was done etirely locally so that I can dedicate all of my empty cpu cores to run the codeql rules which reduce the scanning time up to 60%.

27 out of 30 plugins passed with 0 findings. Following are the plugins that gave few findings :

The rules were updated respectively so that these plugins also do not give any result. With this the current set of rules if ran on the top 30 plugins will generate no noise.

Then I focused on the pr related to plugin-repo-cli and generator-joplin, updated the code tested them using a dedicated published test package which is a clone of updated plugin-repo-cli and raised 2 prs :

  1. Tools: Resolves #16012: Add GitHub authentication and issue submission to publish script by akshajrawat · Pull Request #16022 · laurent22/joplin · GitHub

  2. Tools: Resolves #15974: Added new publish plugin command in plugin-repo-cli by akshajrawat · Pull Request #15981 · laurent22/joplin · GitHub

Both the prs are independent of each other.

Also, added a new workflow that runs when each time any of the codeql rules are changed. It runs those rules in top 20 plugins and makes sure no result are found in any of the plugin. This is the workflow : plugins-test/.github/workflows/rule-regression-test.yml at master · akshajrawat/plugins-test · GitHub

I will be updating the GitHub - joplin/plugins-test · GitHub repository with all of the code shortly since some changes are underway right now, after doing the necessary changes and make sure everything works, I'll update the repository.

Edit : updated : GitHub - joplin/plugins-test · GitHub

2 Likes