
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.
Inject the appropriate logger and set up connection parameters:
Freddy = require 'freddy'
Freddy.addErrorListener(listener)
Freddy.connect('amqp://guest:guest@localhost:5672', {logger}).done (freddy) ->
continueWith(freddy)
, (error) ->
doSthWithError(error)
See http://www.squaremobius.net/amqp.node/ssl.html for available options.
sslOptions = {
cert: fs.readFileSync('clientcert.pem'),
key: fs.readFileSync('clientkey.pem'),
ca: [fs.readFileSync('cacert.pem')]
}
Freddy.connect('amqps://localhost:5671', {logger, ...sslOptions}).done (freddy) ->
continueWith(freddy)
, (error) ->
doSthWithError(error)
These message queues have been tested and are working with Freddy. Other queues can be added easily:
Sends a message to the given destination. If there is no consumer then the
message stays in the queue until somebody consumes it.
freddy.deliver destination, message
Sends a message to the given destination. If nobody consumes the message in
timeout seconds then the message is discarded. This is useful for showing
notifications that must happen in a certain timeframe but where we don't really
care if it reached the destination or not.
freddy.deliver destination, message, timeout: 5
Sends a message to the given destination. Has a default timeout of 3 and
discards the message from the queue if a response hasn't been returned in that
time.
freddy.deliver destination, message, (response) ->
# ...
, (error) ->
# ...
Sends a message to the given destination. Keeps the message in the queue if
a timeout occurs.
freddy.deliver destination, message, timeout: 4, deleteOnTimeout: false, (response) ->
# ...
, (error) ->
# ...
freddy.respondTo destination, (message, handler) ->
if true
handler.success(id: 5)
else
handler.error(error: 'something went wrong')
.done (responderHandler) ->
doSthWith(responderHandler)
When it's necessary to receive messages but not consume them, consider tapping.
responderHandler = freddy.tapInto(pattern, callback)
destination refers to the destination that the message was sent topattern :
# matching 0 or more words* matching exactly one wordExamples:
freddy.tapInto "i.#.free", (message, handler) ->
# ...
receives messages that are delivered to "i.want.to.break.free"
freddy.tapInto "somebody.*.love", (message, handler) ->
# ...
receives messages that are delivered to somebody.to.love but doesn't receive messages delivered to someboy.not.to.love
freddy was originally written by Urmas Talimaa as part of SaleMove development team.

freddy is maintained and funded by SaleMove, Inc.
The names and logos for SaleMove are trademarks of SaleMove, Inc.
FAQs
Simple messaging API supporting acknowledgements and request-response
The npm package freddy receives a total of 10 weekly downloads. As such, freddy popularity was classified as not popular.
We found that freddy demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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
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.