postman-collection 4.4.0

Enables developers to use a unified Postman Collection format Object across projects

postman-collection@4.4.0 was published on 2024-02-28. Its manifest declares 11 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=10.

All postman-collection versions · Permanent reference to 4.4.0 · Latest release

Package specifications

Version4.4.0
License declarationApache-2.0
Published2024-02-28T09:19:22.792Z
Node.js requirement>=10
Type declarationsNot declared
Runtime dependency count11
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size495.50 KiB
Published file count43
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies17
Repository stars501
Repository forks240

Install postman-collection 4.4.0

npm install postman-collection@4.4.0
pnpm add postman-collection@4.4.0
yarn add postman-collection@4.4.0

Runtime dependencies

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.

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.

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

Evidence and freshness