Is node-postgres-named safe to use?

node-postgres-named has no known vulnerabilities on the latest version (2.4.1). DepScope rates its health at 48/100 (high risk).

What is the latest version of node-postgres-named?

The latest version of node-postgres-named is 2.4.1, released 2016-10-18.

Does node-postgres-named have known vulnerabilities?

No known vulnerabilities on the latest version of node-postgres-named.

Is node-postgres-named deprecated?

No, node-postgres-named is actively maintained. Latest release: 2.4.1 (2016-10-18).

What are alternatives to node-postgres-named?

Popular alternatives to node-postgres-named in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does node-postgres-named use?

License information for node-postgres-named is not declared in the registry metadata.

node-postgres-named

npmv2.4.1

Named parameters for node-postgres.

16 versions1 maintainers1 deps6,737 weekly dl

bwestergard/node-postgres-named

/ 100

Health

use with caution

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

Moderate health score (48/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

lodash

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/node-postgres-named