
Research
Supply Chain Attack on Axios Pulls Malicious Dependency from npm
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
@baselime/lambda-logger
Advanced tools
The library offers a straightforward logging solution for Node.js-based AWS Lambda functions, requiring no external dependencies.
const { logger } = require("@baselime/lambda-logger");
logger.info("This is an informational message", {
operation: "copy-paste-replace",
count: 9000,
});
The library provides an object that includes four logging functions - info,
warn, debug, and error - enabling you to log messages with varying levels
of severity. By setting the LOG_LEVEL environment variable, you can control
the visibility of the logs. The library is incredibly easy to use, with no
external dependencies. It enhances console.log with useful defaults.
npm install @baselime/lambda-logger
const { logger } = require("@baselime/lambda-logger");
logger.info("This is an informational message", { payload: { foo: "bar" } });
logger.warn("This is a warning message", { payload: { foo: "bar" } });
logger.debug("This is a debug message", { payload: { foo: "bar" } });
logger.error("This is an error message", { payload: { foo: "bar" } });
By default, the library only prints logs with a severity level of info or higher. However, you can control the logging level by setting the LOG_LEVEL environment variable to one of the following values:
DEBUG: All log messages will be printed.INFO (default): Only messages with a severity level of info, warn, or
error will be printed.WARN: Only messages with a severity level of warn or error will be
printed.ERROR: Only messages with a severity level of error will be printed.Additionally, you can use the wrap method to instrument your AWS Lambda
function and gain visibility of its trigger event and response, which can be
helpful when debugging.
const { wrap, logger } = require("@baselime/lambda-logger");
exports.handler = wrap(async (event, context) => {
logger.info("Lambda function started");
try {
const result = await someAsyncFunction();
logger.debug("Result", result);
return result;
} catch (error) {
logger.error("Error", error);
throw error;
}
});
We also support Middy The lambda middleware framework.
import { Baselime, logger } from "@baselime/lambda-logger";
import middy from "@middy/core";
exports.handler = middy()
.use(Baselime())
.handler(function (e, context) {
const requests = e.Records.map((el) =>
Buffer.from(el.kinesis.data, "base64").toString("utf-8")
);
logger.info("The events to stream", requests);
});
If you would like to contribute to the development of this library, please submit a pull request on GitHub.
This library is licensed under the MIT License. See the LICENSE file for details.
FAQs
An opinionated logger for AWS Lambda
The npm package @baselime/lambda-logger receives a total of 1,780 weekly downloads. As such, @baselime/lambda-logger popularity was classified as popular.
We found that @baselime/lambda-logger 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
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.

Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.

Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.