You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "<p>Amity Tech Store Audit reads WordPress and WooCommerce configuration, analyzes the standard WooCommerce catalog, and produces a Store Health Score with clear findings.</p>\n<p>Amity Tech Store Audit is developed by <a href=\"https://amity-tech.com/\" rel=\"nofollow ugc\">Amity Tech</a>. Buyer-configurable agency branding remains independent and blank by default.</p>\n<p>It does not automatically change store data. It does not test payment transactions or email delivery, scan for malware, optimize performance, or contact an external service.</p>\n<p>The 84-check set covers:</p>\n<ul>\n<li>WordPress environment and basic configuration.</li>\n<li>WooCommerce core page, policy-content, and store setup.</li>\n<li>Standard WooCommerce product catalog data.</li>\n<li>Core shipping-zone configuration.</li>\n<li>Enabled payment gateway status and manual testing reminders.</li>\n<li>Conservative WooCommerce Core tax-setting review.</li>\n<li>WooCommerce sender and Core order-email configuration.</li>\n</ul>\n<p>Reports can be downloaded as HTML or CSV. A print-friendly report can be saved as PDF through the browser print dialog.</p>\n<p>Amity Tech Store Audit retains a bounded 20-scan history and identifies findings that are new, worsened, improved, or resolved. Administrators can ignore intentional findings for background alerts without changing the finding status or score.</p>\n<p>Optional daily or weekly background alerts are disabled by default. Administrators can create up to five independently enabled jobs with separate site-timezone schedules. All jobs share the saved recipients and alert baseline. WordPress sends a minimal email digest only for new or worsened Critical and Warning findings. The email excludes customer, order, payment, credential, and finding-evidence data.</p>\n<p>The dashboard and reports visualize Store Health Score and Critical-finding trends from the bounded history. An optional target is informational only and does not alter scoring or guarantee store operation. Each scheduled job can use a selected site-timezone hour and weekly day.</p>\n<p>Dashboard, History, Amity Tech Store Audit Settings, and Test Email are separate tabs. Test-email results are displayed within the Test Email tab beside the action.</p>\n<p>WP-CLI users can run and store a scan, inspect the latest status, or export JSON, CSV, and HTML through <code>wp amity-tech-store-audit</code>. JSON uses a stable allowlisted schema. CLI/report output can contain privileged configuration evidence, so generated files and CI logs should be protected.</p>\n",
37
+
"installation": "<ol>\n<li>Upload the <code>amity-tech-store-audit</code> folder to <code>/wp-content/plugins/</code> or install the packaged ZIP.</li>\n<li>Activate Amity Tech Store Audit in WordPress.</li>\n<li>Ensure a supported version of WooCommerce is active.</li>\n<li>Open WooCommerce > Amity Tech Store Audit.</li>\n<li>Select Run Scan.</li>\n</ol>\n",
38
+
"faq": "\n<dt id=\"does%20amity%20tech%20store%20audit%20change%20products%20or%20settings%3F\">\nDoes Amity Tech Store Audit change products or settings?\n</h4>\n<p>\n<p>No. A scan reads and reports on existing data. Navigation buttons only open the relevant WordPress or WooCommerce screen.</p>\n</p>\n<dt id=\"does%20an%20enabled%20payment%20gateway%20result%20prove%20payments%20work%3F\">\nDoes an enabled payment gateway result prove payments work?\n</h4>\n<p>\n<p>No. Amity Tech Store Audit never creates an order or payment transaction. End-to-end payment testing is always a manual requirement.</p>\n</p>\n<dt id=\"is%20the%20store%20health%20score%20a%20security%20score%3F\">\nIs the Store Health Score a security score?\n</h4>\n<p>\n<p>No. Amity Tech Store Audit is not a security scanner and the score is not a guarantee that a store is secure, legally compliant, accessible, fast, or ready to launch.</p>\n</p>\n<dt id=\"does%20it%20support%20third-party%20product%20types%2C%20gateways%2C%20shipping%20methods%2C%20themes%2C%20or%20page%20builders%3F\">\nDoes it support third-party product types, gateways, shipping methods, themes, or page builders?\n</h4>\n<p>\n<p>Version 1 audits WordPress Core, WooCommerce Core, and standard WooCommerce product types. It does not promise compatibility with third-party implementations.</p>\n</p>\n<dt id=\"does%20ignoring%20a%20finding%20improve%20the%20score%3F\">\nDoes ignoring a finding improve the score?\n</h4>\n<p>\n<p>No. Ignore only suppresses future background email alerts for that check. The original status, evidence, report, and deterministic score remain unchanged.</p>\n</p>\n<dt id=\"why%20did%20a%20scheduled%20scan%20run%20late%3F\">\nWhy did a scheduled scan run late?\n</h4>\n<p>\n<p>Amity Tech Store Audit uses WordPress Cron. On a low-traffic site, an event may run after its scheduled time unless the host invokes WordPress Cron from a real server cron job.</p>\n</p>\n<dt id=\"does%20an%20accepted%20alert%20email%20prove%20delivery%3F\">\nDoes an accepted alert email prove delivery?\n</h4>\n<p>\n<p>No. Amity Tech Store Audit records whether WordPress accepted the message through <code>wp_mail()</code>. It does not test SMTP or guarantee inbox delivery.</p>\n</p>\n<dt id=\"can%20i%20run%20amity%20tech%20store%20audit%20from%20wp-cli%3F\">\nCan I run Amity Tech Store Audit from WP-CLI?\n</h4>\n<p>\n<p>Yes. Use <code>wp amity-tech-store-audit scan</code>, <code>wp amity-tech-store-audit status</code>, or <code>wp amity-tech-store-audit report --format=json|csv|html</code>. WP-CLI is treated as a trusted server-shell context. Store generated output securely because findings may describe privileged store configuration.</p>\n</p>\n<dt id=\"does%20amity%20tech%20store%20audit%20provide%20seo%2C%20tax%2C%20or%20legal%20advice%3F\">\nDoes Amity Tech Store Audit provide SEO, tax, or legal advice?\n</h4>\n<p>\n<p>No. Version 0.7.0 does not integrate with third-party SEO plugins. Tax and policy checks report Core configuration conservatively and always require qualified professional review where applicable.</p>\n</p>\n\n",
39
+
"changelog": "<h4>0.7.0</h4>\n<ul>\n<li>Renamed the plugin to Amity Tech Store Audit for WooCommerce with a new slug, text domain, namespace, and WP-CLI command.</li>\n<li>Updated all plugin-owned option, transient, cron, nonce, filter, and action identifiers to the new vendor prefix.</li>\n<li>Removed the previous product name to avoid confusion with an unrelated third-party product.</li>\n</ul>\n<h4>0.6.1</h4>\n<ul>\n<li>Added Amity Tech as the plugin Author, with standards-compliant company links in plugin metadata, the directory readme, and the administration screen.</li>\n<li>Added Amity Tech Co., Ltd. legal attribution to the bundled documentation and license notice.</li>\n<li>Preserved the previous compatibility identifiers and buyer-configurable agency branding before the 0.7.0 rename.</li>\n</ul>\n<h4>0.6.0</h4>\n<ul>\n<li>Added separate Amity Tech Store Audit Settings and Test Email administration tabs.</li>\n<li>Kept test-email result messages inside the Test Email tab after submission.</li>\n<li>Added up to five independently enabled daily or weekly background scan jobs.</li>\n<li>Added per-job site-timezone schedule controls and next-run visibility.</li>\n<li>Added automatic migration from the previous single background schedule.</li>\n</ul>\n<h4>0.5.0</h4>\n<ul>\n<li>Added WP-CLI scan, status, and JSON/CSV/HTML report commands.</li>\n<li>Added a stable, versioned, allowlisted JSON export schema.</li>\n<li>Added five conservative WooCommerce Core tax-configuration checks.</li>\n<li>Added three Core refund/privacy/policy-content checks.</li>\n<li>Added four WooCommerce sender and Core order-email configuration checks.</li>\n<li>Added WP-CLI scan-source tracking to bounded history and trends.</li>\n</ul>\n<h4>0.4.0</h4>\n<ul>\n<li>Added an accessible server-rendered Store Health Score and Critical-finding trend.</li>\n<li>Added the same bounded trend to HTML and print/PDF reports without a chart library.</li>\n<li>Added an optional informational maintenance target that does not alter scoring.</li>\n<li>Added a validated report brand color and plain-text agency identity in email.</li>\n<li>Added site-timezone schedule hour and weekly-day controls with DST-aware single-event scheduling.</li>\n</ul>\n<h4>0.3.0</h4>\n<ul>\n<li>Added a bounded history of the 20 most recent manual and scheduled scans.</li>\n<li>Added deterministic new, worsened, improved, and resolved change detection.</li>\n<li>Added a capability- and nonce-protected ignore/restore workflow for alert suppression.</li>\n<li>Added opt-in daily or weekly WordPress Cron scans and minimal email alerts.</li>\n<li>Added a manual test email using saved recipients and the latest Critical and Warning results.</li>\n<li>Added alert baselines and retry eligibility when WordPress cannot accept an email.</li>\n<li>Added finding sorting by checklist order, severity, change type, category, or check name.</li>\n</ul>\n<h4>0.2.0</h4>\n<ul>\n<li>Expanded the read-only checklist from 53 to 72 checks.</li>\n<li>Added cached WordPress update, site identity, and pending administrator-email checks.</li>\n<li>Added WooCommerce page-content, price-format, and tax-rate checks.</li>\n<li>Added catalog sale data, downloadable file, external/grouped product, and backorder checks.</li>\n<li>Added free-shipping condition and payment checkout-copy checks.</li>\n</ul>\n<h4>0.1.2</h4>\n<ul>\n<li>Added scan progress feedback and duplicate-submission protection.</li>\n<li>Added interactive status filters for dashboard findings.</li>\n<li>Added a Plugins-screen shortcut and menu-location guidance.</li>\n</ul>\n<h4>0.1.1</h4>\n<ul>\n<li>Declared compatibility with WooCommerce High-Performance Order Storage (HPOS).</li>\n</ul>\n<h4>0.1.0</h4>\n<ul>\n<li>Initial development version.</li>\n<li>Added 53 read-only checks across five categories.</li>\n<li>Added deterministic Store Health Score and administrator dashboard.</li>\n<li>Added HTML, CSV, and print/PDF report flows.</li>\n</ul>\n"
40
+
},
41
+
"short_description": "Read-only WooCommerce store audits for launch, handoff, and maintenance checks.",
42
+
"description": "<p>Amity Tech Store Audit reads WordPress and WooCommerce configuration, analyzes the standard WooCommerce catalog, and produces a Store Health Score with clear findings.</p>\n<p>Amity Tech Store Audit is developed by <a href=\"https://amity-tech.com/\" rel=\"nofollow ugc\">Amity Tech</a>. Buyer-configurable agency branding remains independent and blank by default.</p>\n<p>It does not automatically change store data. It does not test payment transactions or email delivery, scan for malware, optimize performance, or contact an external service.</p>\n<p>The 84-check set covers:</p>\n<ul>\n<li>WordPress environment and basic configuration.</li>\n<li>WooCommerce core page, policy-content, and store setup.</li>\n<li>Standard WooCommerce product catalog data.</li>\n<li>Core shipping-zone configuration.</li>\n<li>Enabled payment gateway status and manual testing reminders.</li>\n<li>Conservative WooCommerce Core tax-setting review.</li>\n<li>WooCommerce sender and Core order-email configuration.</li>\n</ul>\n<p>Reports can be downloaded as HTML or CSV. A print-friendly report can be saved as PDF through the browser print dialog.</p>\n<p>Amity Tech Store Audit retains a bounded 20-scan history and identifies findings that are new, worsened, improved, or resolved. Administrators can ignore intentional findings for background alerts without changing the finding status or score.</p>\n<p>Optional daily or weekly background alerts are disabled by default. Administrators can create up to five independently enabled jobs with separate site-timezone schedules. All jobs share the saved recipients and alert baseline. WordPress sends a minimal email digest only for new or worsened Critical and Warning findings. The email excludes customer, order, payment, credential, and finding-evidence data.</p>\n<p>The dashboard and reports visualize Store Health Score and Critical-finding trends from the bounded history. An optional target is informational only and does not alter scoring or guarantee store operation. Each scheduled job can use a selected site-timezone hour and weekly day.</p>\n<p>Dashboard, History, Amity Tech Store Audit Settings, and Test Email are separate tabs. Test-email results are displayed within the Test Email tab beside the action.</p>\n<p>WP-CLI users can run and store a scan, inspect the latest status, or export JSON, CSV, and HTML through <code>wp amity-tech-store-audit</code>. JSON uses a stable allowlisted schema. CLI/report output can contain privileged configuration evidence, so generated files and CI logs should be protected.</p>\n",
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments