@log4js-node/log4js-api

v1.0.2

For libraries that want to include log4js for logging, but don't want to introduce version conflicts for users that also use log4js. Delegates to whatever log4js version can be found, but does not introduce a specific log4js version. For more information about how to use this package see README

Latest version published 6 years ago

License: Apache-2.0

NPM

GitHub

Package Health Score

47 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

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.0.2	\|	08/2018	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

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

Recognized

Weekly Downloads (64,641)

GitHub Stars: 32
Forks: 9
Contributors: 3

Direct Usage Popularity

The npm package @log4js-node/log4js-api receives a total of 64,641 downloads a week. As such, we scored @log4js-node/log4js-api popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package @log4js-node/log4js-api, we found that it has been starred 32 times.

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

Community

Limited

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

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like @log4js-node/log4js-api is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 1
Open PR: 1
Last Release: 6 years ago
Last Commit: 6 years ago

Further analysis of the maintenance status of @log4js-node/log4js-api 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 @log4js-node/log4js-api 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: 0 Direct
Versions: 4
Install Size: 15 kB
Dist-tags: 1
# of Files: 6
Maintainers: 2
TS Typings: Yes

@log4js-node/log4js-api 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

Log4js - API

This library is intended for use by other library makers that want to include support for log4js in their libraries without requiring a dependency on a specific version of log4js. It is intended that this library should remain static, and will work with any version of log4js. If no version of log4js can be found, then the library simply does not output anything.

Installation

npm install @log4js-node/log4js-api

Usage

Use as you would log4js - only without configuring it, it would be your library's clients that are responsible for configuring log4js (if they want to). The API is limited to only getLogger on the log4js object, and returns a Logger object that only supports the basic log functions (trace, debug, info, warn, error, fatal). If log4js is found in the require path, then the real log4js Logger object is returned.

const log4js = require('@log4js-node/log4js-api');
const logger = log4js.getLogger('my-library');

logger.info("Library starting up");

@log4js-node/log4js-api development dependencies

codecov eslint husky nyc sandboxed-module tap validate-commit-msg

FAQs

What is @log4js-node/log4js-api?

For libraries that want to include log4js for logging, but don't want to introduce version conflicts for users that als... Visit Snyk Advisor to see a full health score report for @log4js-node/log4js-api, including popularity, security, maintenance & community analysis.

Is @log4js-node/log4js-api popular?

The npm package @log4js-node/log4js-api receives a total of 64,641 weekly downloads. As such, @log4js-node/log4js-api popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @log4js-node/log4js-api well maintained?

We found indications that @log4js-node/log4js-api is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @log4js-node/log4js-api safe to use?

The npm package @log4js-node/log4js-api was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 13 November-2024, at 06:06 (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