ProShop Storefront Child Theme for WooCommerce

What You Should Do / Checklist To make sure your installation of ProShop 2.0.16 is as safe as possible, do the following: Use an official, unmodified versionGet the child theme from WooCommerce.com or the developer, not from dubious GPL or membership sources. Compare files / audit codeCompare your installed child theme files with the original (if possible) to see if any malicious modifications exist (unexpected eval(), base64 encoding, external resource URLs). Keep parent theme and all plugins updatedSince ProShop depends on Storefront and WooCommerce, vulnerabilities in those are as (or more) important. Review overridden templates / custom PHPCheck any overridden templates or custom code in your child theme for missing sanitization, escaping, use of unsafe functions. Minimize external script usageIf loading external scripts, load from trusted sources over HTTPS, ideally with subresource integrity (SRI) if possible. Use security scanning toolsUse plugins like Wordfence, Sucuri, or code scanners to detect malicious changes or vulnerabilities. BackupsMaintain regular backups of code + database so you can recover from issues. Test on stagingBefore updates or changes, test everything (especially custom template overrides) on a staging environment to catch issues. Restrict permissionsOnly allow trusted users to edit theme files, upload new themes, or change child theme settings. Verdict ProShop 2.0.16 is a relatively low-risk component by itself, because it’s a child theme (so it usually does not handle heavy logic). The real risk is in how the child theme is implemented, whether it's been modified, and how securely the rest of the site is built (parent theme, plugins, server environment). If you use an official, clean copy, audit the overrides, and maintain plugin/parent updates, using ProShop child theme is acceptable in many WooCommerce setups.