CleanFeed for YouTube: Hide Shorts, Block Channels & Keywords 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: iikgdocegpniapcigmmgcnacfojmmnnd
Permissions (3)
- Execute scripts in pages
Related extensions
YouTube Channel Blocker & Video FilterLifestyle
Clean YouTube: Block Shorts, Hide Recommended Videos & CommentsProductivity
YouTube Clean: Block Shorts, Filter Recommendations & Skip AdsProductivity
YouTube Feed Cleaner - Hide Shorts & Filter VideosProductivity
YouTube Shorts Blocker – Hide & Disable ShortsMake Chrome Yours
Feed Cleaner for YouTubeProductivity
Frequently asked questions
Is CleanFeed for YouTube: Hide Shorts, Block Channels & Keywords safe to use?
Our latest automated scan rates the Chrome listing of CleanFeed for YouTube: Hide Shorts, Block Channels & Keywords at 82/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 CleanFeed for YouTube: Hide Shorts, Block Channels & Keywords require?
CleanFeed for YouTube: Hide Shorts, Block Channels & Keywords requests 3 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops CleanFeed for YouTube: Hide Shorts, Block Channels & Keywords?
Check the developer line on the store listing before installing — impersonators copy popular extension names.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.4.1
- Current listed version
- 1.4.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.