Is named-logs-for-servers safe to use?

named-logs-for-servers has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 33/100 (critical risk).

What is the latest version of named-logs-for-servers?

The latest version of named-logs-for-servers is 0.1.0, released 2024-10-24.

Does named-logs-for-servers have known vulnerabilities?

No known vulnerabilities on the latest version of named-logs-for-servers.

Is named-logs-for-servers deprecated?

No, named-logs-for-servers is actively maintained. Latest release: 0.1.0 (2024-10-24).

What are alternatives to named-logs-for-servers?

Popular alternatives to named-logs-for-servers in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does named-logs-for-servers use?

named-logs-for-servers is licensed under MIT.

named-logs-for-servers

npmv0.1.0

minimal logging facet for libraries forked for servers

License MITpermissive2 versions1 maintainers0 deps

wighawag/named-logs-for-servers

/ 100

Health

use with caution

[email protected] low health (33/100) — consider alternatives

Moderate health score (33/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

2.9 KBminified

1.2 KB gzipped

0 direct dependencies

ESMside effects

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/named-logs-for-servers