SECURITY REPORT · EXTENSHI SCAN
Revision History: Writing Process Visibility for Google Docs & Slides
Chrome extension·by Revision History
49
/ 100 SAFETY SCORE
RISKY
Several elevated signals. Read the findings before sharing this with your team.
Automated analysis of publicly available code — not a professional security audit. It may produce false positives and does not prove an extension is unsafe or safe. Treat it as one signal among many. Disclaimer · Report an issue
How it ranks
Revision History: Writing Process Visibility for Google Docs & Slides's safety score vs every other extension we've scanned
Globally
2%of extensions carry more risk
Riskier ←→ Safer
Ranked against 397,380 extensions
In Productivity
2%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 191,263 productivity extensions
Findings
112
median 16Lower is safer
Critical findings
1
median 0Severity = Critical
Permissions
1
median 3Declared in manifest
Active users
300000
median 14vs category median
Findings breakdown
Automated security signal · 112 distinct issues across 6 severities
112
distinct issues
detected
detected
Scanners reported 168 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical11%
High1413%
Needs Review00%
Medium5448%
Low3329%
Info109%
Permissions requested
1 permission declared
No risky permissions
1 permission requested — none are flagged as risky.
Medium
Store local data
Can save data locally in the browser for persistence
Are you the author of Revision History: Writing Process Visibility for Google Docs & Slides?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show Revision History: Writing Process Visibility for Google Docs & Slides's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 4, 2026
Browser extensions made transparent.