@automattic/vip-go-internal-cli
Advanced tools
Internal CLI tools for the VIP team at Automattic
Internal CLI Tools for VIP Staff.
Make sure you have an open connection to the Automattic proxy and are able to tunnel local traffic to port 8080.
npm i -g @automattic/vip-go-internal-cli
vipgo config set PROXY=socks://127.0.0.1:8080
vipgo login
Make sure you allow HTTPS traffic to pixel.wp.com (the domain the CLI connects to in order to track command usage) otherwise your output will be polluted with the following error:
❌ Unexpected error. Please use the escalation pathways to resolve this issue:
🌐 https://wp.me/PCYsg-FSf
Error: connect ECONNREFUSED 0.0.0.0:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
E.g. on PiHole, use sudo pihole -w pixel.wp.com.
Show available commands:
vipgo --help
You can append --help to any sub-command to see options and sub-sub-commands.
For details about contributing to this project (e.g. setting up development environment, publishing a release, etc.), please see CONTRIBUTING.md.
FAQs
Internal CLI tools for the VIP team at Automattic
We found that @automattic/vip-go-internal-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 20 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.