pkg-conf 4.0.0
Get namespaced config from the closest package.json
pkg-conf@4.0.0 was published on 2021-09-02. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^12.20.0 || ^14.13.1 || >=16.0.0.
All pkg-conf versions · Permanent reference to 4.0.0 · Latest release
Package specifications
| Version | 4.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2021-09-02T16:09:35.810Z |
| Node.js requirement | ^12.20.0 || ^14.13.1 || >=16.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 8.59 KiB |
| Published file count | 5 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 118 |
| Repository forks | 10 |
Install pkg-conf 4.0.0
npm install pkg-conf@4.0.0 pnpm add pkg-conf@4.0.0 yarn add pkg-conf@4.0.0
Runtime dependencies
- find-up ^6.0.0
- load-json-file ^7.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- find-up@6.3.0 — direct
- load-json-file@7.0.1 — direct
- locate-path@7.2.0 — indirect
- p-limit@4.0.0 — indirect
- p-locate@6.0.0 — indirect
- path-exists@5.0.0 — indirect
- yocto-queue@1.2.2 — indirect
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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 10/10 — security policy file detected |
| Code-Review | 2/10 — Found 7/30 approved changesets -- score normalized to 2 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/pkg-conf/4.0.0 — retrieved 2026-10-29T10:10:09.611Z
- https://api.deps.dev/v3/projects/github.com%2Fsindresorhus%2Fpkg-conf — retrieved 2026-10-29T08:23:37.221Z
- https://api.deps.dev/v3/systems/npm/packages/pkg-conf/versions/4.0.0 — retrieved 2026-10-29T10:10:10.141Z
- https://api.deps.dev/v3/systems/npm/packages/pkg-conf/versions/4.0.0:dependencies — retrieved 2026-10-29T10:10:10.175Z