Linkedin Cli

4. Authenticate (opens browser for OAuth):

linkedin-cli auth

5. Verify: linkedin-cli whoami

Security

• Credentials: Stored in ~/.config/linkedin-cli/.env (read by dotenv at runtime). Set chmod 600 to restrict access.
• No postinstall scripts: The package has zero install scripts — verify via npm pack --dry-run or inspect package.json.
• No telemetry or network calls except to the official LinkedIn API (api.linkedin.com) and OAuth (www.linkedin.com) when you run a command.
• Pinned install: The install command pins to a specific release tag. Audit the source at https://github.com/0xmythril/linkedin-cli before installing.
• Dependencies: Only 3 runtime deps — commander (CLI parsing), dotenv (env file loading), open (browser launch for OAuth). No transitive dependencies beyond these.

Commands

Verify auth

linkedin-cli whoami

Authenticate

linkedin-cli auth

Post a text update

linkedin-cli post "Your post text here"

Share a URL with commentary

linkedin-cli share "https://example.com/article" "Your commentary here"

Delete a post

linkedin-cli delete <post-id-urn-or-url>
linkedin-cli delete https://www.linkedin.com/feed/update/urn:li:activity:7654321/

Important rules

• Do NOT post unless the user explicitly asks or a cron job triggers it. LinkedIn rate-limits API usage.
• Always confirm with the user before posting or sharing. Show them the text first.
• Keep posts professional — LinkedIn is a professional network.
• linkedin-cli accepts raw numeric IDs, full URNs, and LinkedIn post URLs.
• If you get a 401 error, the token has expired (~60 days). Ask the user to run linkedin-cli auth to re-authenticate.
• This tool is for posting only. It cannot read feeds, search profiles, or send messages.