TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: lbppdbcjnfacljmmkjpcogchlpjnmboe
Permissions (4)
- Execute scripts in pages
Related extensions
Web Table to CSV Exporter – Copy HTML Tables to SheetsProductivity
TableGrab — Export any table to CSV & ExcelProductivity
Table to CSV & Excel: One-Click Web Table ExportProductivity
TableGrab — Table to CSV & ExcelProductivity
TableHarvest – Export Tables to Excel, CSV & SheetsProductivity
GrabTable – Table to Excel & CSVProductivity
Frequently asked questions
Is TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes safe to use?
Our latest automated scan rates the Chrome listing of TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes at 77/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes require?
TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes requests 4 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes?
TableHarvest: Export Tables to Excel, CSV & Sheets by HeroBytes is published by HeroBytes. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.0.1
- Current listed version
- 1.0.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.