
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).
github-actions-utils
Advanced tools
Common utils JS/TS Github Action
npm install github-actions-utils
Extract available inputs to the object and check theirs types:
import { actionInputs, transformIfSet } from 'github-actions-utils';
const myActionInputs = {
// required
input1: actionInputs.getString('input1', true),
secretInput2: actionInputs.getString('secretInput2',
true, // required
true // set value as secret
),
// cast to int (or throw), optional
intInput: actionInputs.getInt('intInput'),
// cast to number (or throw), optional,
floatInput: actionInputs.getFloat('floatInput'),
// return absolute path from relative to GITHUB_WORKSPACE, required
pathInput: actionInputs.getWsPath('pathInput', true),
// read string input (optional) and transform it to array (split by | sign)
arrayInput: transformIfSet(actionInputs.getString('arrayInput', false), s => s.split('|')),
};
Extract available outputs to the object:
import { ActionOutput, ActionTrOutput } from 'github-actions-utils';
const myActionOutputs = {
output1Name: new ActionOutput('output1Name'),
// accepts array, joins it to string using | glue
arrayOutput2Name: new ActionTrOutput('arrayOutput2Name', v => v.join('|')),
// accepts boolean value, converts to 'true' or 'false' string
boolOutputName: new ActionTrOutput<boolean>('boolOutputName', b => b ? 'true' : 'false'),
};
// Calls setOutput(...) inside
myActionOutputs.output1Name.setValue('output1value');
myActionOutputs.arrayOutput2Name.setValue(['el1', 'el2']);
myActionOutputs.boolOutputName.setValue(true);
myActionOutputs.arrayOutput2Name.getValue(); // -> ['el1', 'el2']
myActionOutputs.arrayOutput2Name.getStringValue(); // -> 'el1|el2'
extensionName: new ActionOutput('extensionName'),
If you use ncc
command to pack your action code (as
github example suggests), you may want to ensure that you
didn't forget to run ncc
command and commit packed js file.
Add script to your package.json
:
...
"scripts": {
"build": "tsc",
"pack": "ncc build",
"all": "npm run build && npm run pack",
"checkPackCommited": "checkIsUnchanged ./dist/index.js" <---- this one
}
...
Add script call in a build-test workflow after pack:
- name: Check pack is up-to-date
run: npm run checkPackCommited
This command will check that after build performed in workflow ./dist/index.js
file remains unchanged.
FAQs
Utils for JS/TS github action
The npm package github-actions-utils receives a total of 2 weekly downloads. As such, github-actions-utils popularity was classified as not popular.
We found that github-actions-utils 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.
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.