
Security News
AI Agent Lands PRs in Major OSS Projects, Targets Maintainers via Cold Outreach
An AI agent is merging PRs into major OSS projects and cold-emailing maintainers to drum up more work.
Handles colourful logging to the console for different log levels without needing to put if statements and console logs throughout your code.
// No more of this:
if (process.env.NODE_ENV === 'development') { console.log('My log message.'); }
// Now we have this:
log.debug('My log message.');
At the top of your application entry point you need to initialise Log-Ninja with a log level, before you require any other files in your application:
const log = require('log-ninja').init('debug');
log.info('Some information...');
Then in any other files in your application you just require Log-Ninja again to get the already initialised version:
const log = require('log-ninja');
// Will be output because "warn" has a lower log level than "debug".
log.warn('A warning 😮');
// Will NOT be output because "verbose" has a higher log level than "debug".
log.verbose('Lots and lots of detail.');
Log-Ninja supports the following log levels:
| ID | Level | Function |
|---|---|---|
| fatal | 0 | log.fatal(string1, string2, ...) |
| error | 1 | log.error(string1, string2, ...) |
| warn | 2 | log.warn(string1, string2, ...) |
| info | 3 | log.info(string1, string2, ...) |
| debug | 4 | log.debug(string1, string2, ...) |
| verbose | 5 | log.verbose(string1, string2, ...) |
Each of the functions support multiple strings which will be concatenated together with spaces (the same way console.log() works).
If you inintialise Log-Ninja like .init('verbose') or .init(6) then ALL logs will be output to the console.
If you inintialise Log-Ninja like .init('error') or .init(1) then only error and fatal logs will be output to the console.
If you don't want colours to be output you can pass a second parameter to .init() like so:
const log = require('log-ninja').init('debug', {
colours: false,
});
Log-Ninja comes with a few other functions to make logging to the console a little bit easier:
| Function | Description |
|---|---|
log.title(string1, string2, ...) | Outputs an important message in bold and underlined. |
log.important(string1, string2, ...) | Outputs an important information in bold. |
log.success(string1, string2, ...) | Outputs a success message. |
log.final(string1, string2, ...) | Outputs the final success message of an execution. |
log.json(object1, object2, ...objectN) | Outputs JSON pretty printed for every object provided. |
log.space() | Outputs a blank line. |
log.raw(aSingleString) | Outputs a single string to stdout without any colours and without a trailing line break. |
log.rawError(aSingleString) | Outputs a single string to stderr without any colours and without a trailing line break. |
log.box(status, message) | Outputs a status followed by a message. Valid statuses are "ok", "fail", "warn" and "info". |
FAQs
Handles logging for different environments: development, staging & production.
We found that log-ninja 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
An AI agent is merging PRs into major OSS projects and cold-emailing maintainers to drum up more work.

Research
/Security News
Chrome extension CL Suite by @CLMasters neutralizes 2FA for Facebook and Meta Business accounts while exfiltrating Business Manager contact and analytics data.

Security News
After Matplotlib rejected an AI-written PR, the agent fired back with a blog post, igniting debate over AI contributions and maintainer burden.