It was a busy week. I’ve a some updates to the Obsidian Plugin Audit or OPA. My biggest focus on how to best do the audit on each plugin. Previously I’d clone the plugins main repo but this ended up being, in retrospect, the wrong approach. This approach had me auditing things that did not need auditing when the focus for this tool is strictly to provide insights for the plugin code that would run locally.
Now the audit is audits the currently release defined in the Obsidian Community Plugins and uses the previous method as a backup. So if the audit shows that it was generated by Obsidian Plugin Audit v1.2.4 or higher the new focus on the plugin release was used.
Now when a finding is detected in a file it’ll only show the main.js, manifest.json or styles.css where before it would show the actual file before being packaged into main.js. This was the only way to not audit files that didn’t need to be audited.
Here’s a list of the other changes:
- Added a share link that links to the plugin url /latest. Ex. https://obsidianpluginaudit.com/audit/peerdraft/latest
- Added a Shield badge link do can be copied and added to the README of the respective plugin in Github. It also updates automatically when the audit score changes in OPA.
- I’ve removed the audit history dropdown from report pages. From now on old audits are deleted prior to creating the new audit.
- Added visible plugin-version chips to every comment and reply now that they’re not tied to a specific audit report. Previously comments would be deleted when the audit report was deleted.
- Audit reports now include the app version that generated the report.
Hot Off The Presses!
Since this was announced just recently I thought I’d include it in this post. Obsidian recently launched a brand new community site and developer dashboard at community.obsidian.md — and it’s somewhat of a big deal. The site lets you browse plugins and themes by popularity, newest, and recently updated. But the most exciting feature? A public scorecard system that breaks down each plugin’s health and risk findings.
What’s cool is that this scoring system closely mirrors what I’ve been building independently over at ObsidianPluginAudit.com — a tool I created to give users deeper insight into plugin risk. Seeing the official Obsidian team move in the same direction validates that this kind of transparency actually matters. If this had been around three weeks ago OPA might now be around today.
There are still differences between what these two sites offer. I get into the new community and dashboard in this video.
