nodejs-logging

v1.1.1

* There are 8 log levels: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL and OFF. * A level can be set via an environment variable LOG_LEVEL, the default isinfo. * There are 2 types of logging output which is set via an environment variable LOG_OUTPUT, t For more information about how to use this package see README

Latest version published 7 years ago

License: MIT

NPM

GitHub

Package Health Score

42 / 100

security
Security review needed
popularity
Limited
maintenance
Inactive
community
Sustainable

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
1.1.1	\|	06/2017	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (1)

GitHub Stars: 0
Forks: 4
Contributors: 20

Direct Usage Popularity

The npm package nodejs-logging receives a total of 1 downloads a week. As such, we scored nodejs-logging popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package nodejs-logging, we found that it has been starred ? times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: No
Contributors: 20
Funding: No

With more than 10 contributors for the nodejs-logging repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like nodejs-logging is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 0
Open PR: 6
Last Release: 7 years ago
Last Commit: 2 years ago

Further analysis of the maintenance status of nodejs-logging based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for nodejs-logging is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 7 years
Dependencies: 4 Direct
Versions: 3
Install Size: 0 B
Dist-tags: 1
# of Files: 0
Maintainers: 1
TS Typings: No

nodejs-logging has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

Logging

There are 8 log levels: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL and OFF.
A level can be set via an environment variable LOG_LEVEL, the default isinfo.
There are 2 types of logging output which is set via an environment variable LOG_OUTPUT, the default issingle.
1. Production - a single line output - LOG_OUTPUT=single.
2. Development - a multi line output - LOG_OUTPUT=multi.
By default logging is turned off when running these unit tests.

Use

yarn add @hmcts/nodejs-logging

// Require it
const logging = require('nodejs-logging');

// Set this config only once
logging.config({ 
    microservice: 'your-service-name', 
    team: 'YOURTEAM'
    environment: 'some-environemnt'
});

// Get your logger
logger = logging.getLogger('app.js');

// Get logging
  logger.info({
    message: 'Yay, logging!'
  });

Optionally you can use the built in express.js access logger.

app.use(logging.express.accessLogger());
~~~

A typical HTTP 404 log error when encountering an error would look like the following.

{ responseCode: 404, message: 'Not Found', fields: [], level: 'ERROR', environment: 'some-environemnt', hostname: 'My-MacBook-Pro.local', rootRequestId: '', requestId: '', originRequestId: '', type: 'nodejs', microservice: 'your-service-name', team: 'YOURTEAM', timestamp: '2017-01-27T11:27:23+00:00' }


#### Units Tests

yarn test

nodejs-logging dependencies

lodash log4js moment on-finished

nodejs-logging development dependencies

chai mocha sinon sinon-chai supertest

FAQs

What is nodejs-logging?

* There are 8 log levels: ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL and OFF. * A level can be set via an environment ... Visit Snyk Advisor to see a full health score report for nodejs-logging, including popularity, security, maintenance & community analysis.

Is nodejs-logging popular?

The npm package nodejs-logging receives a total of 1 weekly downloads. As such, nodejs-logging popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is nodejs-logging well maintained?

We found indications that nodejs-logging is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is nodejs-logging safe to use?

While scanning the latest version of nodejs-logging, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 12 November-2024, at 19:50 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP