Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 05:15 UTC

microsoft / window-post-message-proxy

A generic messaging component for orchestrating promise based messages to/from a hosting application and an iframed component over the window.postMessage API.

TypeScript · JavaScriptCustom license★ 57 stars⑂ 19 forkssince Jun 2016View on GitHub ↗

microsoft/window-post-message-proxy holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (88/100) and lowest on Vitality (13/100). It was last updated 644 days ago. 5 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

MicrosoftOrganization
125,510 followers8,208 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmwindow-post-message-proxy0.3.01,261,74912153 days agowindowpostmessagepostmessageiframeproxy

Metrics by category

Vitality

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

13Critical · 21% of overall
How it's scored
0/36Push recencylast push 644 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share
days_since_last_push644
active_weeks_last_year0
How it's scored
16.2/27Ships releases8 version tags (no GitHub releases)
0/36Release recencylatest release 2,447 days ago
12.6/27Release cadencea release every ~175.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv0.2.6
releases_from_tagsyes
days_since_latest_release2,447
mean_days_between_releases175.8
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?

71Good · 17% of overall
How it's scored
28.4/60Stars57 stars
10.5/25Forks19 forks
8/15Watchers29 watchers
Inputs used
forks19
stars57
watchers29
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads1,261,749 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageswindow-post-message-proxy
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,261,749
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?

88Excellent · 23% of overall
How it's scored
45.9/54Bus factor5 contributor(s) cover half of all commits
19.1/22.5Commit distributiontop contributor authored 15% of commits
13.5/13.5Contributor breadth19 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor5
contributors_sampled19
top_contributor_share0.152
How it's scored
0/42Issue resolutionno issues or no data
18.8/30PR acceptance10/16 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs10
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs6
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach125,510 followers of microsoft
25/25Track record8,208 public repos, account ~12 yr old
Inputs used
followers125,510
owner_typeOrganization
is_verified
owner_loginmicrosoft
public_repos8,208
account_age_days4,605
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 153 days ago
20/20Version history12 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageswindow-post-message-proxy
ecosystemsnpm
any_deprecatedno
min_days_since_publish153

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config.eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://microsoft.github.io/window-post-message-proxy
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://microsoft.github.io/window-post-message-proxy
docs_sitehttps://microsoft.github.io/window-post-message-proxy
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:window-post-message-proxy@0.3.0 runtime dependency closure — what installing the published package pulls in — 1 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.js
11/11Static type checkingtsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/7 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes19,664
source_files_sampled7
oversized_source_files0

Key facts

57GitHub stars
19contributors
0commits, last 12 months
644days since last push
8releases
5bus factor
0open issues
npmpackage ecosystems

More detail

Star and fork history 57 ★ / 0 ⇿
57Stars

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.

01020304050605732016-082021-032025-10

Each point covers 9 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-07-21 05:15 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmes6-promise^3.1.2package.json
All dependencies 37

Full resolved dependency set from the GitHub dependency graph: 1 direct and 36 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npmes6-promise^3.1.2direct
npm@types/es6-promise^3.3.0indirect
npm@types/jasmine^3.5.10indirect
npm@types/jquery^3.3.34indirect
npm@types/karma-jasmine^3.1.0indirect
npm@types/node^14.14.7indirect
npm@types/npm^2.0.31indirect
npm@typescript-eslint/eslint-plugin^4.7.0indirect
npm@typescript-eslint/parser^4.7.0indirect
npmdel^2.2.1indirect
npmeslint^7.13.0indirect
npmeslint-plugin-import^2.22.1indirect
npmeslint-plugin-jsdoc^30.7.7indirect
npmeslint-plugin-prefer-arrow^1.2.2indirect
npmgulp^4.0.2indirect
npmgulp-eslint^6.0.0indirect
npmgulp-help-four^0.2.3indirect
npmgulp-prepend^0.3.0indirect
npmgulp-rename^1.2.2indirect
npmgulp-replace^0.5.4indirect
npmgulp-uglify^3.0.2indirect
npmgulp4-run-sequence^1.0.1indirect
npmjasmine-core^2.4.1indirect
npmjquery^3.6.0indirect
npmkarma^6.3.17indirect
npmkarma-chrome-launcher^1.0.1indirect
npmkarma-coverage^2.2.0indirect
npmkarma-jasmine^1.0.2indirect
npmkarma-sourcemap-loader^0.3.7indirect
npmkarma-spec-reporter0.0.26indirect
npmts-loader^9.2.8indirect
npmtypedoc^0.22.15indirect
npmtypescript^4.4.4indirect
npmuglify-save-license^0.4.1indirect
npmwebpack^5.71.0indirect
npmwebpack-stream^7.0.0indirect
npmyargs^17.4.1indirect
Dependency advisories 0

Installing npm:window-post-message-proxy@0.3.0 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.17.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.