Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 19:02 UTC

microsoftgraph / msgraph-typescript-typings

Microsoft Graph TypeScript Type Definitions

PowerShell · TypeScriptCustom license★ 130 stars⑂ 34 forkssince Jul 2016View on GitHub ↗

microsoftgraph/msgraph-typescript-typings holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Community & Adoption (75/100) and lowest on Vitality (40/100). It was last updated 126 days ago. 3 contributors account for most of its recent work.

73
overall / 100
Good

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.

73
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 64 is calibrated to 73 on the published index scale (record calibration 2026-08-02).

Ownership

Microsoft GraphOrganization
1,444 followers236 public repossince Feb 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@microsoft/microsoft-graph-types2.43.14,365,32287327 days ago

Metrics by category

Vitality

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

40Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 126 days ago
4.2/36Commit cadence6/52 weeks with commits
11.9/18Commit volume20 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_year20
human_commit_share0.23
days_since_last_push126
active_weeks_last_year6
How it's scored
27/27Ships releases70 releases published
16.2/36Release recencylatest release 327 days ago
12.6/27Release cadencea release every ~142 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count70
latest_release_tagv2.43.1
releases_from_tagsno
days_since_latest_release327
mean_days_between_releases142
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?

75Good · 17% of overall
How it's scored
34.2/60Stars130 stars
12.7/25Forks34 forks
7.9/15Watchers27 watchers
Inputs used
forks34
stars130
watchers27
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads4,365,322 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@microsoft/microsoft-graph-types
dependents
ecosystemsnpm
total_downloads
monthly_downloads4,365,322
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?

75Good · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16.1/22.5Commit distributiontop contributor authored 29% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 12 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled19
top_contributor_share0.286
How it's scored
21.4/42Issue resolution51% of issues closed
13.9/30PR acceptance383/829 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_prs383
open_issues26
closed_issues27
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.509
closed_unmerged_prs446
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
22.7/25Owner reach1,444 followers of microsoftgraph
25/25Track record236 public repos, account ~10 yr old
Inputs used
followers1,444
owner_typeOrganization
is_verifiedno
owner_loginmicrosoftgraph
public_repos236
account_age_days3,843
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 327 days ago
20/20Version history87 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@microsoft/microsoft-graph-types
ecosystemsnpm
any_deprecatedno
min_days_since_publish327

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests16 out of 21 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://graph.microsoft.com
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsmicrosoft-graph-typescript, typescript-definitions, intellisense, microsoft-graph-models, devxeng
has_wikiyes
homepagehttps://graph.microsoft.com
docs_sitehttps://graph.microsoft.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.8/2.5CI-Tests16 out of 21 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 12 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate 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
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
4.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities17 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories17
affected_packages7
assessed_packages88
unassessed_packages0
affected_by_severityhigh 5, moderate 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 88 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30.1/40Legible commit history13 of 23 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.565
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance39 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.39
How it's scored
27/45Type-checkable codePowerShell with type-check config (tsconfig.json)
41.2/55Manageable file sizes1/4 source files over 60KB
Inputs used
primary_languagePowerShell
largest_source_bytes2,057,941
source_files_sampled4
oversized_source_files1

Key facts

130GitHub stars
19contributors
20commits, last 12 months
126days since last push
70releases
3bus factor
26open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 34 ⇿
0Stars
34Forks
70Releases

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.

01325383422016-092021-082026-07
Major 1Minor 67Patch 2

Each point covers 9 days.

OpenSSF Scorecard 6.0 / 10
6.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-08-27 19:02 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
7CI-Tests16 out of 21 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities17 existing vulnerabilities detected
All dependencies 88

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

RegistryPackageVersionRelation
npm@babel/runtime7.21.0indirect
npm@isaacs/cliui8.0.2indirect
npm@microsoft/microsoft-graph-client3.0.7indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/chai5.2.2indirect
npm@types/deep-eql4.0.2indirect
npm@types/node24.10.2indirect
npmansi-regex5.0.1indirect
npmansi-regex6.1.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.1indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion2.0.1indirect
npmbrowser-stdout1.3.1indirect
npmcamelcase6.3.0indirect
npmchai6.2.2indirect
npmchalk4.1.2indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcross-spawn7.0.6indirect
npmdebug4.3.5indirect
npmdecamelize4.0.0indirect
npmdiff7.0.0indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmforeground-child3.3.0indirect
npmget-caller-file2.0.5indirect
npmglob10.4.5indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjackspeak3.4.3indirect
npmjs-yaml4.1.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmlru-cache10.4.3indirect
npmminimatch9.0.5indirect
npmminipass7.1.2indirect
npmmocha11.7.5indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpicocolors1.1.1indirect
npmrandombytes2.1.0indirect
npmreaddirp4.1.2indirect
npmregenerator-runtime0.13.11indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.2.1indirect
npmserialize-javascript6.0.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.1.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtslib2.5.0indirect
npmtypescript5.9.3indirect
npmundici-types7.16.0indirect
npmwhich2.0.2indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 7

This repository publishes no package the index resolves, so its own dependency graph was assessed — 88 packages, which also include development and test pins that never ship: 7 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion2.0.1indirecthigh55.0.9
glob10.4.5indirecthigh111.1.0
js-yaml4.1.0indirecthigh44.3.1
minimatch9.0.5indirecthigh310.2.3
serialize-javascript6.0.2indirecthigh27.0.5
@babel/runtime7.21.0indirectmoderate18.0.0-alpha.17
diff7.0.0indirectmoderate18.0.3

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 statisticsnpm.