pg 7.9.0

PostgreSQL client - pure javascript & libpq with the same API

pg@7.9.0 was published on 2019-03-15. Its manifest declares 7 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 4.5.0.

All pg versions · Permanent reference to 7.9.0 · Latest release

Package specifications

Version7.9.0
License declarationMIT
Published2019-03-15T18:43:15.127Z
Node.js requirement>= 4.5.0
Type declarationsNot declared
Runtime dependency count7
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size91.97 KiB
Published file count20
Package typeNot declared
ES module entryNot declared
Default entry./lib
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars13228
Repository forks1373

Install pg 7.9.0

npm install pg@7.9.0
pnpm add pg@7.9.0
yarn add pg@7.9.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 28 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Code-Review7/10 — Found 21/29 approved changesets -- score normalized to 7
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness