Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-03 11:05 UTC

microsoftgraph / msgraph-sdk-go

Microsoft Graph SDK for Go

GoMIT★ 331 stars⑂ 42 forkssince Oct 2021View on GitHub ↗

microsoftgraph/msgraph-sdk-go holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on AI Readiness (65/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

89
overall / 100
Excellent

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.

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

Ownership

Microsoft GraphOrganization
1,424 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
Gogithub.com/microsoftgraph/msgraph-sdk-gov1.100.0-18123 days ago

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 12 days ago
22.2/36Commit cadence32/52 weeks with commits
18/18Commit volume130 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year130
human_commit_share0.58
days_since_last_push12
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 23 days ago
27/27Release cadencea release every ~24.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv1.100.0
releases_from_tagsno
days_since_latest_release23
mean_days_between_releases24.2
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
40.9/60Stars331 stars
13.4/25Forks42 forks
6.8/15Watchers18 watchers
Inputs used
forks42
stars331
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicespkg.go.dev
has_pull_request_templateyes

Sustainability & Governance

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

76Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.8/22.5Commit distributiontop contributor authored 65% of commits
13.5/13.5Contributor breadth23 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.653
How it's scored
36.9/42Issue resolution88% of issues closed
22.3/30PR acceptance481/648 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 2/3 approved changesets -- score normalized to 6
Inputs used
merged_prs481
open_issues36
closed_issues261
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.879
closed_unmerged_prs167
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 domainverified-domain status not read for this organization
22.7/25Owner reach1,424 followers of microsoftgraph
25/25Track record235 public repos, account ~10 yr old
Inputs used
followers1,424
owner_typeOrganization
is_verified
owner_loginmicrosoftgraph
public_repos235
account_age_days3,819
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 go
35/35Publish recencylatest publish 23 days ago
20/20Version history181 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/microsoftgraph/msgraph-sdk-go
ecosystemsgo
any_deprecatedno
min_days_since_publish23

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
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://docs.microsoft.com/en-us/graph/sdks/sdks-overview
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsgo, sdk, microsoft-graph, microsoft-graph-sdk, devxeng
has_wikino
homepagehttps://docs.microsoft.com/en-us/graph/sdks/sdks-overview
docs_sitehttps://docs.microsoft.com/en-us/graph/sdks/sdks-overview
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 2/3 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 11 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.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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.8/7.5Vulnerabilities9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.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
advisories10
affected_packages3
assessed_packages25
unassessed_packages0
affected_by_severitymoderate 1, unknown 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 25 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.

65Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history45 of 58 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.776
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapgo.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
6/10Demonstrated agent practice3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance16 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.03
toolchain_manifestsgo.mod
dependency_bot_commit_share0.16
How it's scored
45/45Type-checkable codeGo (statically typed)
54.9/55Manageable file sizes19/16,202 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes308,423
source_files_sampled16,202
oversized_source_files19

Key facts

331GitHub stars
23contributors
130commits, last 12 months
12days since last push
100releases
1bus factor
36open issues
Gopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 42 ⇿
0Stars
42Forks
100Releases

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.

010203040504222021-112024-032026-07
Major 1Minor 97Patch 2

Each point covers 5 days.

OpenSSF Scorecard 5.9 / 10
5.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-08-03 11:05 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
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 2/3 approved changesets -- score normalized to 6
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Gogithub.com/Azure/azure-sdk-for-go/sdk/azcorev1.21.1go.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/microsoft/kiota-abstractions-gov1.9.4go.mod
Gogithub.com/microsoft/kiota-serialization-form-gov1.1.3go.mod
Gogithub.com/microsoft/kiota-serialization-json-gov1.1.2go.mod
Gogithub.com/microsoft/kiota-serialization-multipart-gov1.1.2go.mod
Gogithub.com/microsoft/kiota-serialization-text-gov1.1.3go.mod
Gogithub.com/microsoftgraph/msgraph-sdk-go-corev1.4.1go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
All dependencies 25

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

RegistryPackageVersionRelation
Gogithub.com/azure/azure-sdk-for-go/sdk/azcorev1.21.1direct
Gogithub.com/google/uuidv1.6.0direct
Gogithub.com/microsoft/kiota-abstractions-gov1.9.4direct
Gogithub.com/microsoft/kiota-serialization-form-gov1.1.3direct
Gogithub.com/microsoft/kiota-serialization-json-gov1.1.2direct
Gogithub.com/microsoft/kiota-serialization-multipart-gov1.1.2direct
Gogithub.com/microsoft/kiota-serialization-text-gov1.1.3direct
Gogithub.com/microsoftgraph/msgraph-sdk-go-corev1.4.1direct
Gogithub.com/stretchr/testifyv1.11.1direct
Gogithub.com/azure/azure-sdk-for-go/sdk/internalv1.12.0indirect
Gogithub.com/cespare/xxhash/v2v2.3.0indirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/go-logr/logrv1.4.3indirect
Gogithub.com/go-logr/stdrv1.2.2indirect
Gogithub.com/microsoft/kiota-authentication-azure-gov1.3.1indirect
Gogithub.com/microsoft/kiota-http-gov1.5.6indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/std-uritemplate/std-uritemplate/go/v2v2.0.3indirect
Gogo.opentelemetry.io/auto/sdkv1.2.1indirect
Gogo.opentelemetry.io/otelv1.43.0indirect
Gogo.opentelemetry.io/otel/metricv1.43.0indirect
Gogo.opentelemetry.io/otel/tracev1.43.0indirect
Gogolang.org/x/netv0.53.0indirect
Gogolang.org/x/textv0.36.0indirect
Gogopkg.in/yaml.v3v3.0.1indirect
Dependency advisories 3

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

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/netv0.53.0indirectmoderate80.56.0
go.opentelemetry.io/otelv1.43.0indirectunknown11.44.0
golang.org/x/textv0.36.0indirectunknown10.39.0

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

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