Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 16:47 UTC

postmanlabs / postman-request

Simplified HTTP request client.

JavaScriptApache-2.0★ 155 stars⑂ 49 forkssince Aug 2016forkView on GitHub ↗

postmanlabs/postman-request holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (78/100) and lowest on Engineering Quality (39/100). It was last updated 37 days ago. 3 contributors account for most of its recent work.

57
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

57
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 55 is calibrated to 57 on the published index scale (record calibration 2026-08-02).

Ownership

Postman Inc.Organization
4,207 followers218 public repossince Dec 2014

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmpostman-request2.88.1-postman.497,240,7817737 days agohttpsimpleutilutility

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

51Moderate · 21% of overall
How it's scored
18/36Push recency — last push 37 days ago
5.5/36Commit cadence — 8/52 weeks with commits
12.9/18Commit volume — 26 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year26
human_commit_share1
days_since_last_push37
active_weeks_last_year8
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 37 days ago
12.6/27Release cadence — a release every ~322.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.88.1-postman.49
releases_from_tagsyes
days_since_latest_release37
mean_days_between_releases322.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

57Moderate · 17% of overall
How it's scored
35.5/60Stars — 155 stars
14/25Forks — 49 forks
7.5/15Watchers — 23 watchers
Inputs used
forks49
stars155
watchers23
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 7,240,781 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespostman-request
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads7,240,781
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

78Good · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.4/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 101 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled100
top_contributor_share0.269
How it's scored
0/42Issue resolution — no issues or no data
21.1/30PR acceptance — 76/108 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 6/15 approved changesets -- score normalized to 4
Inputs used
merged_prs76
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs32
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 4,207 followers of postmanlabs
25/25Track record — 218 public repos, account ~11 yr old
Inputs used
followers4,207
owner_typeOrganization
is_verifiedno
owner_loginpostmanlabs
public_repos218
account_age_days4,268

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 37 days ago
20/20Version history — 77 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespostman-request
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

39Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

1Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeno
has_docs_dirno
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2/2.5CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 6/15 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 101 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
12.4/35Direct dependencies free of known advisories — 2 affected: uuid 8.3.2 (high 7.5), qs 6.14.2 (moderate 5.3)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
30.3/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 126 days ago
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages72
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages2
Matched the npm:postman-request@2.88.1-postman.49 runtime dependency closure — what installing the published package pulls in — 72 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://nodejs.org/llms.txt)
19.2/40Legible commit history — 36 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://nodejs.org/llms.txt
legible_history_share0.36
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.6/55Manageable file sizes — 1/128 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes66,111
source_files_sampled128
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

155GitHub stars
100contributors
26commits, last 12 months
37days since last push
100releases
3bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 49 ⇿
0Stars
49Forks
98Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

010203040504932016-102021-092026-08
Major 0Minor 13Patch 13

Each point covers 10 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-27 16:46 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 6/15 approved changesets -- score normalized to 4
10Contributorsproject has 101 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
npm@postman/form-data~3.1.1package.json
npm@postman/tough-cookie~4.1.3-postman.1package.json
npm@postman/tunnel-agent^0.6.8package.json
npmaws-sign2~0.7.0package.json
npmaws4^1.12.0package.json
npmcaseless~0.12.0package.json
npmcombined-stream~1.0.6package.json
npmextend~3.0.2package.json
npmforever-agent~0.6.1package.json
npmhttp-signature~1.4.0package.json
npmis-typedarray~1.0.0package.json
npmisstream~0.1.2package.json
npmjson-stringify-safe~5.0.1package.json
npmmime-types^2.1.35package.json
npmoauth-sign~0.9.0package.json
npmqs~6.14.1package.json
npmsafe-buffer^5.1.2package.json
npmsocks-proxy-agent^8.0.5package.json
npmstream-length^1.0.2package.json
npmuuid^8.3.2package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 2

Installing npm:postman-request@2.88.1-postman.49 pulls in 72 packages, direct and transitive: 2 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
uuid8.3.2directhigh113.0.1
qs6.14.2directmoderate16.15.2

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.