Package Health Score

80 / 100

security
No known security issues
popularity
Influential project
maintenance
Sustainable
community
Sustainable

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

Version				Vulnerabilities	License Risk
7.0.0	\|	08/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.0.0	\|	10/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.1.0	\|	12/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.1.0	\|	03/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.0	\|	04/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

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

Influential project

Weekly Downloads (16,453,892)

GitHub Stars: 749
Forks: 33
Contributors: 20

Direct Usage Popularity

The npm package log-symbols receives a total of 16,453,892 downloads a week. As such, we scored log-symbols popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package log-symbols, we found that it has been starred 749 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: No
Code of Conduct: Yes
Contributors: 20
Funding: Yes

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

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 5 months ago
Last Commit: 5 months ago

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

We found that log-symbols demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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: >=18

Age: 10 years
Dependencies: 2 Direct
Versions: 14
Install Size: 4.4 kB
Dist-tags: 1
# of Files: 8
Maintainers: 1
TS Typings: No

log-symbols 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.

Not sure how to use log-symbols?

To help you get started, we've collected the most common ways that log-symbols is being used within popular public projects.

phenomic / phenomic / packages / core / src / logger / __tests__ / index.js View on Github

const log = logger("sender test", false);

  // we can't snapshot because of logSymbols & colors...
  const colorStart =
    process.platform !== "win32" && !process.env.CIRCLECI ? "[90m" : "";
  const colorEnd =
    process.platform !== "win32" && !process.env.CIRCLECI ? "[39m" : "";

  expect(log("test msg")).toBe(
    `${logSymbols.info} ${colorStart}sender test:${colorEnd} test msg`,
  );
  expect(log.debug("test debug")).toBe(
    `  ${colorStart}sender test:${colorEnd} test debug`,
  );
  expect(log.info("test info")).toBe(
    `${logSymbols.info} ${colorStart}sender test:${colorEnd} test info`,
  );
  expect(log.success("test success")).toBe(
    `${logSymbols.success} ${colorStart}sender test:${colorEnd} test success`,
  );
  expect(log.warn("test warning")).toBe(
    `${logSymbols.warning} ${colorStart}sender test:${colorEnd} test warning`,
  );
  expect(log.error("test error")).toBe(
    `${logSymbols.error} ${colorStart}sender test:${colorEnd} test error`,
  );
});

View more ways to use log-symbols

log-symbols

> Colored symbols for various log levels

Includes fallbacks for Windows CMD which only supports a limited character set.

Install

npm install log-symbols

Usage

import logSymbols from 'log-symbols';

console.log(logSymbols.success, 'Finished successfully!');
// Terminals with Unicode support:     ✔ Finished successfully!
// Terminals without Unicode support:  √ Finished successfully!

API

logSymbols

info

success

warning

error

figures - Unicode symbols with Windows CMD fallbacks
py-log-symbols - Python port
log-symbols - Ruby port
guumaster/logsymbols - Golang port

log-symbols dependencies

is-unicode-supported yoctocolors

log-symbols development dependencies

ava strip-ansi tsd xo

FAQs

What is log-symbols?

Colored symbols for various log levels. Example: `✔︎ Success`. Visit Snyk Advisor to see a full health score report for log-symbols, including popularity, security, maintenance & community analysis.

Is log-symbols popular?

The npm package log-symbols receives a total of 16,453,892 weekly downloads. As such, log-symbols popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is log-symbols well maintained?

We found indications that log-symbols maintenance is sustainable demonstrating some project activity. We saw a total of 20 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is log-symbols safe to use?

The npm package log-symbols 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 30 December-2024, at 02:16 (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