Send to Cursor for GitHub 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: pjagjodoppglflmcpmdhcaifkjnegdpf
Permissions (1)
- Store local data
Related extensions
Frequently asked questions
Is Send to Cursor for GitHub safe to use?
Our latest automated scan rates the Chrome listing of Send to Cursor for GitHub at 98/100 (low 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 Send to Cursor for GitHub require?
Send to Cursor for GitHub requests 1 permission. The most significant: Store local data. See the full breakdown in the security report.
Who develops Send to Cursor for GitHub?
Send to Cursor for GitHub is published by Muneyasu Kagawa. 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.1.1
- Current listed version
- 1.1.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.