PostInk – AI Reply Generator & Tweet Scheduler for X 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: eemhknloebdnnbeoencocekmmmndlelm
Permissions (7)
- Store local data
- Add context menu items
- Schedule tasks
Related extensions
HumanPost for XProductivity
XposterAI: AI Replies + Scheduler Studio for X/TwitterProductivity
PostOwl - Twitter & X Reply / Post GeneratorLifestyle
X-Reply: AI Reply & Comment Generator for X (Twitter)Productivity
TweeterAI — Smart Tweet & Reply Generator for Twitter/XProductivity
TweetBlink - AI Tweet Generator for Optimized X/Twitter PostsProductivity
Frequently asked questions
Is PostInk – AI Reply Generator & Tweet Scheduler for X safe to use?
Our latest automated scan rates the Chrome listing of PostInk – AI Reply Generator & Tweet Scheduler for X at 78/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 PostInk – AI Reply Generator & Tweet Scheduler for X require?
PostInk – AI Reply Generator & Tweet Scheduler for X requests 7 permissions. The most significant: Store local data, Add context menu items, Schedule tasks. See the full breakdown in the security report.
Who develops PostInk – AI Reply Generator & Tweet Scheduler for X?
PostInk – AI Reply Generator & Tweet Scheduler for X is published by Atif M.. 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.0
- Current listed version
- 1.0.0
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 critical and 9 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.