SECURITY REPORT · EXTENSHI SCAN
AfterFeed
Chrome extension·by David Guo
0
/ 100 SAFETY SCORE
CAUTION
Mostly fine, but a few things worth reviewing before you install.
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
AfterFeed's safety score vs every other extension we've scanned
Globally
31%of extensions carry more risk
Riskier ←→ Safer
Ranked against 357,609 extensions
In Productivity
41%of productivity extensions carry more risk
Riskier ←→ Safer
Ranked against 177,115 productivity extensions
Findings
44
median 16Lower is safer
Critical findings
0
median 0Severity = Critical
Permissions
3
median 3Declared in manifest
Active users
4
median 14vs category median
Findings breakdown
Automated security signal · 44 distinct issues across 6 severities
44
distinct issues
detected
detected
Scanners reported 46 raw occurrences; repeats of the same issue at the same location are merged here. The list below shows every occurrence.
Critical00%
High12%
Needs Review00%
Medium1125%
Low2966%
Info37%
Permissions requested
3 permissions declared
No risky permissions
3 permissions requested — none are flagged as risky.
Medium
Access user identity
Can get OAuth2 tokens and access your Google account identity
Medium
Store local data
Can save data locally in the browser for persistence
Low
Schedule tasks
Can schedule periodic background tasks
Are you the author of AfterFeed?
Claim this extension to respond to findings, add context, and earn a verified badge on extenshi.io.
Add the badge to your README
Show AfterFeed's live security score on GitHub or in your docs
Scan performed by extenshi.io · Aug 25, 2026
Browser extensions made transparent.