
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Get to work as quick as possible.
This is an experiment and right now only works on OSX with iTerm2.
npm install phlow -g
You can use phlow in two ways:
~/.phlow directory and put the JSON files there.phlow.json files in the working directory of each project. In this case you need to set up the PHLOW_HOMEDIR env variable. This tells phlow where your projects are. For example I use /Users/gimenete/projects. Phlow will look in all the subdirectories of the PHLOW_HOMEDIR. By default PHLOW_HOMEDIR is your home directory.A configuration file looks like this
{
"dir": "/Users/gimenete/projects/backbeam-lambda-ui",
"iTerm": {
"tabs": [
{
"panels": [
{
"commands": [
"npm run watch"
]
},
{
"split": "vertically",
"commands": [
"npm start"
]
},
{
"split": "horizontally",
"commands": [
"atom ."
]
}
]
}
]
}
}
So you could save that file as:
~/.phlow/project_name.json$PHLOW_HOMEDIR/project_name/phlow.json. In this case you don't need to put the dir in the configuration file.Finally run:
phlow project_name
The project name doesn't need to be strictly equal. Phlow will look for the most similar directory name with a phlow.json file on it or the most similar configuration file under ~/.phlow. Also, phlow will always ask for confirmation before running anything.
FAQs
Get to work as quick as possible
We found that phlow demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.