Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
express-fp
Advanced tools
Type safe request handlers for Express. TypeScript compatible.
Below is small example that demonstrates request body and query validation using io-ts and fully typed response construction using express-result-types.
const Body = t.interface({
name: t.string,
});
const Query = t.interface({
age: NumberFromString,
});
const requestHandler = wrap(req => {
const jsonBody = req.body.asJson();
const maybeQuery = Query.decode({
age: req.query.get('age').toNullable(),
}).mapLeft(formatValidationErrors('query'));
const maybeBody = jsonBody.chain(jsValue =>
jsValue.validate(Body).mapLeft(formatValidationErrors('body')),
);
return maybeQuery
.chain(query => maybeBody.map(body => ({ query, body })))
.map(({ query, body }) =>
Ok.apply(
new JsValue({
// We defined the shape of the request body and the request query parameter
// 'age' for validation purposes, but it also gives us static types! For
// example, here the type checker knows the types:
// - `body.name` is type `string`
// - `age` is type `number`
name: body.name,
age: query.age,
}),
jsValueWriteable,
),
)
.getOrElseL(error => BadRequest.apply(new JsValue(error), jsValueWriteable));
});
app.post('/', requestHandler);
// ❯ curl --request POST --silent --header 'Content-Type: application/json' \
// --data '{ "name": "bob" }' "localhost:8080/" | jq '.'
// "Validation errors for query: Expecting NumberFromString at age but instead got: null."
// ❯ curl --request POST --silent --header 'Content-Type: application/json' \
// --data '{ "name": "bob" }' "localhost:8080/?age=foo" | jq '.'
// "Validation errors for query: Expecting NumberFromString at age but instead got: \"foo\"."
// ❯ curl --request POST --silent --header 'Content-Type: invalid' \
// --data '{ "name": "bob" }' "localhost:8080/?age=5" | jq '.'
// "Expecting request header 'Content-Type' to equal 'application/json', but instead got 'invalid'."
// ❯ curl --request POST --silent --header 'Content-Type: application/json' \
// --data 'invalid' "localhost:8080/?age=5" | jq '.'
// "JSON parsing error: Unexpected token i in JSON at position 0"
// ❯ curl --request POST --silent --header 'Content-Type: application/json' \
// --data '{ "name": 1 }' "localhost:8080/?age=5" | jq '.'
// "Validation errors for body: Expecting string at name but instead got: 1."
// ❯ curl --request POST --silent --header 'Content-Type: application/json' \
// --data '{ "name": "bob" }' "localhost:8080/?age=5" | jq '.'
// {
// "name": "bob",
// "age": 5
// }
yarn add express-fp
yarn
npm run compile
npm run lint
FAQs
Type safe request handlers for [Express]. TypeScript compatible.
The npm package express-fp receives a total of 14 weekly downloads. As such, express-fp popularity was classified as not popular.
We found that express-fp 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.