
Research
/Security News
Critical Vulnerability in NestJS Devtools: Localhost RCE via Sandbox Escape
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
High-volume Amazon SQS Poller and single-queue client for Node.js 16 and up with full typescript support
The library is production ready and is being stress used in a full blown production environment
Please see full documentation here
import {Squiss, Message} from 'squiss-ts';
const awsConfig = {
credentials: {
accessKeyId: 'accessKeyId',
secretAccessKey: 'secretAccessKey',
},
region: '<region>',
};
const squiss = new Squiss({
awsConfig,
queueName: 'my-sqs-queue',
bodyFormat: 'json',
maxInFlight: 15
});
squiss.on('message', (message: Message) => {
console.log(`${message.body.name} says: ${JSON.stringify(message.body.message)} and has attripute p1 with value ${message.attributes.p1}`);
message.del();
});
squiss.start();
const messageToSend = {
name: 'messageName',
message: {
a: 1,
b: 2,
},
};
const propsToSend = {
p1: 1,
p2: 2,
};
squiss.sendMessage(messageToSend, 0, propsToSend);
npm install squiss-ts
Squiss processes as many messages simultaneously as possible.
Set the maxInFlight option to the number of messages your app can handle at one time without choking, and Squiss will keep
that many messages flowing through your app, grabbing more as you mark each message as handled or ready for deletion.
If the queue is empty, Squiss will maintain an open connection to SQS, waiting for any messages that appear in real time.
Squiss can also handle renewing the visibility timeout for your messages until you handle the message, or message handling time
(set up by you) has passed (see autoExtendTimeout).
Bonus: Squiss will also automatically handle the message attributes formatting and parsing when receiving and sending messages.
Squiss supports Node 6 LTS and higher.
This project is a typescript port (with better performance, bug fixes and new features) of the wonderful and unmaintnaed project TomFrost/Squiss
Squiss was originally created at TechnologyAdvice in Nashville, TN.
All contributions are happily welcomed!
Please make all pull requests to the master
branch from your fork and ensure tests pass locally.
FAQs
High-volume SQS poller
The npm package squiss-ts receives a total of 4,888 weekly downloads. As such, squiss-ts popularity was classified as popular.
We found that squiss-ts demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 0 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
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
Product
Customize license detection with Socket’s new license overlays: gain control, reduce noise, and handle edge cases with precision.
Product
Socket now supports Rust and Cargo, offering package search for all users and experimental SBOM generation for enterprise projects.