linkedin-cli automates LinkedIn outreach via undocumented APIs and browser session cookies. This document outlines expectations for responsible use, data handling, and security.
This tool exists for targeted, professional outreach — not bulk scraping, spam, or harassment.
- Use it to connect with real prospects you'd genuinely want to talk to.
- Built-in rate limits (3s between API calls, 20 leads/batch max) exist for a reason. Don't bypass them.
- Exercise judgment. If your outreach volume feels aggressive, it probably is.
- You are solely responsible for how you use this tool and for compliance with LinkedIn's Terms of Service.
Automated access to LinkedIn may violate their User Agreement.
- The author acknowledges this risk and does not encourage ToS violations.
- You accept all risk of account restrictions, bans, or legal action from LinkedIn.
- This tool is provided as-is. No warranties, express or implied.
All data stays on your machine. Nothing phones home.
- Scraped leads are stored locally in
data/leads.jsonl. - No data is sent to third-party services, analytics, or remote servers.
leads.jsonlis gitignored — never commit personal data to version control.- You must handle scraped data responsibly under applicable privacy laws (GDPR, CCPA, etc.).
- If someone asks you to delete their data, do it.
- No credentials stored. Authentication uses your existing browser session cookie.
- No API keys or tokens in code. Nothing to leak.
- Always run
--dry-runbefore any live operation to preview what will happen. - The human review gate is mandatory — you confirm every action before it executes.
- Review
data/leads.jsonlbefore sending connection requests or messages.
If you discover a security vulnerability:
- Email: security@zonicdesign.art
- Do not open public GitHub issues for security vulnerabilities.
- Allow reasonable time for a response before any public disclosure.
This project is licensed under CC BY-NC-ND 4.0. No commercial use, no derivatives.
- The author assumes no liability for how this tool is used.
- No warranty of any kind — fitness, merchantability, or otherwise.
- Use at your own risk.
See also: README · CONTRIBUTING · LICENSE