Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
@homer0/simple-logger
Advanced tools
A small service to log messages in the console.
⚠️ This package is only for Node.
import { simpleLogger } from '@homer0/simple-logger';
const logger = simpleLogger();
logger.log('Starting the app');
// Will log the message the same way `console.log` would.
if (usingExperimentalFeature()) {
logger.warn('WARNING: This feature is experimental');
// Will log a yellow message.
}
if (onDevelopment()) {
logger.info('Running on a development environment');
// Will log a gray message.
}
if (loadConfiguration()) {
logger.success('The configuration was successfully loaded');
// Will log a green message
}
try {
methodThatMayThrowAnError();
} catch (error) {
logger.error('Damn it!', error);
// Will log `Damn it!` on red, and the `error` stack trace information on `gray`.
}
This was demonstrated on the example above:
success(message)
will log a green message.warn(message)
will log a yellow message.error(message)
will log a red message.info(message)
will log a gray message.But they all depend on this method: log(message, color)
; it allows you to specify one of the colors available on the colors
package.
By default, it uses the console default text color, but you can specify a different color for the message.
logger.log('Starting the app', 'green');
All the methods support both a single message or an Array
of them:
logger.info(['App running', 'connection detected', 'starting Skynet...']);
// This will log three gray messages.
You can even specify a color for each message:
logger.success([
'It works!',
['wait, something is happening', 'gray'],
'Nevermind, Skynet is up and running!',
]);
// This will log the first and third message on green and the second one on gray.
When creating the logger, you can specify a prefix
option that will be prepended to each message.
const logger = simpleLogger({ prefix: 'my-app' });
logger.log('Starting the app');
// Will log `[my-app] Starting the app`
The same way you can specify the prefix when creating the logger, you also have a showTime
option that will make the logger show the current date and time on each message.
const logger = simpleLogger({ showTime: true });
logger.log('Starting the app');
// Will log something like `[2022-06-25 19:41:11] Starting the app`
Yes, you can use both
prefix
andshowTime
together.
If your app uses a Jimple container, you can register SimpleLogger
as the simpleLogger
service by using its provider:
import { simpleLoggerProvider } from '@homer0/simple-logger';
// ...
container.register(simpleLoggerProvider);
// ...
const logger = container.get('simpleLogger');
And since the provider is a "provider creator" (created with my custom version of Jimple), you can customize its service name:
container.register(
simpleLoggerProvider({
serviceName: 'myLogger',
}),
);
The package has an alternative service provider for Jimple that gets the project name from the package.json
and uses as the prefix:
import { appLoggerProvider } from '@homer0/simple-logger';
// ...
container.register(appLoggerProvider);
// ...
const logger = container.get('appLogger');
logger.log('Starting the app');
// Will log `[my-app] Starting the app`, where `my-app` is the `name` in
// your package.json
You can also specify a appLoggerPrefix
on your package.json
, and it will use that instead of the name
.
The "app logger provider" depends on the following services, and it will try to find them in the container, otherwise, it will create new instances:
@homer0/package-info
, with the name packageInfo
. Used to get the project's package.json
information.@homer0/path-utils
, with the name pathUtils
. Needed by package-info
to generate the paths relative to the project root.If you already implement the dependencies, but with a different name, you can specify them in the provider:
container.register(
appLoggerProvider({
services: {
packageInfo: 'myPackageInfo',
pathUtils: 'myPathUtils',
},
}),
);
As this project is part of the packages
monorepo, some of the tooling, like lint-staged
and husky
, are installed on the root's package.json
.
Task | Description |
---|---|
lint | Lints the package. |
test | Runs the unit tests. |
build | Transpiles the project. |
types:check | Validates the TypeScript types. |
FAQs
A small service to log messages in the console
The npm package @homer0/simple-logger receives a total of 16 weekly downloads. As such, @homer0/simple-logger popularity was classified as not popular.
We found that @homer0/simple-logger demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.