@parcel/node-resolver-core 3.6.4

@parcel/node-resolver-core@3.6.4 was published on 2025-06-20. 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 >= 16.0.0.

All @parcel/node-resolver-core versions · Permanent reference to 3.6.4 · Latest release

Package specifications

Version3.6.4
License declarationMIT
Published2025-06-20T23:46:51.309Z
Node.js requirement>= 16.0.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 size31.30 KiB
Published file count7
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars44007
Repository forks2303

Install @parcel/node-resolver-core 3.6.4

npm install @parcel/node-resolver-core@3.6.4
pnpm add @parcel/node-resolver-core@3.6.4
yarn add @parcel/node-resolver-core@3.6.4

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.

Maintained0/10 — 0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review1/10 — Found 3/28 approved changesets -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Binary-Artifacts5/10 — binaries present in source code
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness