# User reviews of community plug ins

**URL:** <https://forum.obsidian.md/t/user-reviews-of-community-plug-ins/46322>\
**Category:** Feature requests\
**Created:** [October 27, 2022, 2:40pm UTC](https://forum.obsidian.md/t/user-reviews-of-community-plug-ins/46322 "2022-10-27T14:40:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rigmarole](https://forum.obsidian.md/user_avatar/forum.obsidian.md/rigmarole/32/29973_2.png) [@rigmarole](https://forum.obsidian.md/u/rigmarole)\
**Post date:** [October 27, 2022, 4:30pm UTC](https://forum.obsidian.md/t/user-reviews-of-community-plug-ins/46322/3 "2022-10-27T16:30:44Z")

</div>

> [@groberts56](#):
>
> and you have to waste a lot of time repairing it.

As a workaround: Personally, I use git as version control. So I can always commit a snapshot before installing a new plugin, and roll back if I have to.

The warnings are clear when you enable community plugins. Whether this feature was ever implemented or not, you should still A) have good backups, B) consider using version control software, C) check the project page of the plugin before installing.

–

There is also a LOT of discussion on the topic here. [Security of the plugins](https://forum.obsidian.md/t/security-of-the-plugins/7544)

---

_[View the full topic](https://forum.obsidian.md/t/user-reviews-of-community-plug-ins/46322)._