Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 23:35 UTC

microsoftgraph / msgraph-beta-typescript-typings

Microsoft Graph Beta TypeScript Type Definitions

TypeScriptCustom license★ 7 stars⑂ 3 forkssince Feb 2021View on GitHub ↗

microsoftgraph/msgraph-beta-typescript-typings holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (82/100) and lowest on AI Readiness (40/100). It was last updated 12 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

Microsoft GraphOrganization
1,418 followers235 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-types-beta0.44.0-preview539,53940293 days ago

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 12 days ago
8.3/36Commit cadence12/52 weeks with commits
14/18Commit volume35 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_year35
human_commit_share
days_since_last_push12
active_weeks_last_year12
How it's scored
27/27Ships releases41 releases published
27/36Release recencylatest release 179 days ago
19.8/27Release cadencea release every ~109.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count41
latest_release_tagv0.46.0-preview
releases_from_tagsno
days_since_latest_release179
mean_days_between_releases109.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?

60Moderate · 17% of overall
How it's scored
12.6/60Stars7 stars
2.5/25Forks3 forks
6.2/15Watchers14 watchers
Inputs used
forks3
stars7
watchers14
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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
76.4/80Monthly downloads539,539 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@microsoft/microsoft-graph-types-beta
dependents
ecosystemsnpm
total_downloads
monthly_downloads539,539
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?

82Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
18.3/22.5Commit distributiontop contributor authored 19% of commits
13.5/13.5Contributor breadth20 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor3
contributors_sampled20
top_contributor_share0.188
How it's scored
37.3/42Issue resolution89% of issues closed
12.9/30PR acceptance107/249 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_prs107
open_issues1
closed_issues8
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.889
closed_unmerged_prs142
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
22.7/25Owner reach1,418 followers of microsoftgraph
25/25Track record235 public repos, account ~10 yr old
Inputs used
followers1,418
owner_typeOrganization
is_verified
owner_loginmicrosoftgraph
public_repos235
account_age_days3,806
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 293 days ago
20/20Version history40 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@microsoft/microsoft-graph-types-beta
ecosystemsnpm
any_deprecatedno
min_days_since_publish293

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicsdevxeng
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.8/2.5CI-Tests7 out of 19 merged PRs checked by a CI test -- score normalized to 3
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
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
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities12 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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
advisories12
affected_packages6
assessed_packages85
unassessed_packages0
affected_by_severityhigh 5, moderate 1
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 85 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.

40Weak · 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
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
41.2/55Manageable file sizes1/4 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes4,254,487
source_files_sampled4
oversized_source_files1

Key facts

7GitHub stars
20contributors
35commits, last 12 months
12days since last push
41releases
3bus factor
1open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-20 23:34 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
3CI-Tests7 out of 19 merged PRs checked by a CI test -- score normalized to 3
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
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
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities12 existing vulnerabilities detected
All dependencies 85

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

RegistryPackageVersionRelation
npm@babel/runtime7.28.4indirect
npm@isaacs/cliui8.0.2indirect
npm@microsoft/microsoft-graph-client3.0.7indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmassertion-error2.0.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion2.0.2indirect
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.4.3indirect
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.1indirect
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.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
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.2indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtslib2.8.1indirect
npmtypescript6.0.2indirect
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 6

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

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion2.0.2indirecthigh25.0.7
glob10.4.5indirecthigh111.1.0
js-yaml4.1.0indirecthigh34.3.0
minimatch9.0.5indirecthigh310.2.3
serialize-javascript6.0.2indirecthigh27.0.5
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.16.0 — full methodology · metrics wiki.

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