Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Pronounced "effin' flow" because it's so badass, fnFlow is a Javascript control flow library heavily influenced by Caolan McMahon's async that encourages a proper functional design pattern.
Pronounced "effin' flow" because it's so badass, fnFlow is a Javascript control flow library heavily influenced by Caolan McMahon's async that encourages a proper functional design pattern.
Like async.auto, it determines the best order for running functions based on their requirements.
For a complicated series of async tasks, using the flow function makes adding new tasks much easier and makes the code more readable. It also encourages you to define functions in places where they can be reused more easily. This makes it an excellent choice for design patterns like MVC where it is a goal to strive for "fat model, skinny controller."
Each function can optionally depend on other functions being completed first, and each function is run as soon as its requirements are satisfied. If any of the functions pass an error to their callback, that function will not complete (so any other functions depending on it will not run) and the main callback will be called immediately with the error. The main callback receives an object containing the results of functions which have completed so far.
Note, all functions are assumed to expect a callback as the final argument, so it is unsafe to pass functions in the tasks object which cannot handle the extra argument.
Arguments
Example
fnFlow.flow({
authorName: 'Brandon Sanderson',
genreName: 'Fantasy',
bookSeriesName: 'The Wheel of Time'
}, {
getAuthor: [Author.getByName, 'authorName'],
getGenre: [Genre.getByName, 'genreName'],
getBookSeries: [BookSeries.getByName, 'bookSeriesName'],
getBooks: [Book.findBooksByAuthorGenreAndBookSeries, 'getAuthor', 'getGenre', 'getBookSeries']
});
Which translates to the following workflow:
To do this using async.auto would look like this:
async.auto({
getAuthor: function(callback, results){
Author.getByName('Brandon Sanderson', callback);
},
getGenre: function(callback, results){
Genre.getByName('Fantasy', callback);
},
getBookSeries: function(callback, results){
BookSeries.getByName('The Wheel of Time', callback);
},
getBooks: ['getAuthor', 'getGenre', 'getBookSeries', function(callback, results){
Book.findBooksByAuthorGenreAndBookSeries(results.getAuthor, results.getGenre, results.getBookSeries, callback);
}]
});
Another Example
fnFlow.flow({
authorName: 'Brandon Sanderson',
genreName: 'Fantasy'
}, {
getAuthor: [Author.getByName, 'authorName'],
getGenre: [Genre.getByName, 'genreName'],
assertGenreExistence: [Genre.assertExistence, 'getGenre'],
getBooks: ['assertGenreExistence', 'getGenre', 'findBooksByAuthor', 'getAuthor']
}, function(err, results) {
if(err) return console.error(err); //genre probably didn't exist.
console.log('Number of books:', results.getBooks.length);
});
Which translates to the following workflow:
Running Multple Sets of Tasks in Parallel
fnFlow.flow([
{ authorName: 'Brandon Sanderson',
genreName: 'Fantasy'
},
{ authorName: 'Jack Vance',
genreName: 'Fantasy'
}
], {
getAuthor: [Author.getByName, 'authorName'],
getGenre: [Genre.getByName, 'genreName'],
assertGenreExistence: [Genre.assertExistence, 'getGenre'],
getBooks: ['assertGenreExistence', 'getGenre', 'findBooksByAuthor', 'getAuthor']
}, function(err, results) {
if(err) return console.error(err); //genre probably didn't exist.
results.forEach(function (result) {
console.log('Number of books for ' + result.getAuthor.name + ':', results.getBooks.length);
});
});
This does the exact same thing as the above example, but does it once for Brandon Sanderson and once for Jack Vance, in parallel.
This library was developed by David Fenster at Shutterstock
Copyright (C) 2013 by Shutterstock Images, LLC
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Pronounced "effin' flow" because it's so badass, fnFlow is a Javascript control flow library heavily influenced by Caolan McMahon's async that encourages a proper functional design pattern.
The npm package fnflow receives a total of 4 weekly downloads. As such, fnflow popularity was classified as not popular.
We found that fnflow demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.