Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-19 03:57 UTC

microsoftgraph / msgraph-sdk-php-core

PHPMIT★ 16 stars⑂ 7 forkssince Jun 2021View on GitHub ↗

microsoftgraph/msgraph-sdk-php-core holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (83/100) and lowest on AI Readiness (33/100). It was last updated 30 days ago. 2 contributors account for most of its recent work.

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

84
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 71 is calibrated to 84 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
Packagistmicrosoft/microsoft-graph-corev3.0.0291,7552460 days ago

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
28.8/36Push recencylast push 30 days ago
4.2/36Commit cadence6/52 weeks with commits
10.6/18Commit volume14 commits in the last year
7/10OpenSSF Scorecard: Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year14
human_commit_share
days_since_last_push30
active_weeks_last_year6
How it's scored
27/27Ships releases24 releases published
36/36Release recencylatest release 60 days ago
19.8/27Release cadencea release every ~100.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count24
latest_release_tagv3.0.0
releases_from_tagsno
days_since_latest_release60
mean_days_between_releases100.1
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?

62Moderate · 17% of overall
How it's scored
19.1/60Stars16 stars
6.5/25Forks7 forks
6/15Watchers13 watchers
Inputs used
forks7
stars16
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
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
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
72.9/80Monthly downloads291,755 downloads/month across packagist
4.7/20Registry dependents4 packages depend on it
Inputs used
packagesmicrosoft/microsoft-graph-core
dependents4
ecosystemspackagist
total_downloads3,953,872
monthly_downloads291,755
unverified_packages_excluded

Sustainability & Governance

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

83Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.9/22.5Commit distributiontop contributor authored 43% of commits
13.5/13.5Contributor breadth32 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled32
top_contributor_share0.426
How it's scored
33.2/42Issue resolution79% of issues closed
26.1/30PR acceptance165/190 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 9/11 approved changesets -- score normalized to 8
Inputs used
merged_prs165
open_issues9
closed_issues34
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.791
closed_unmerged_prs25
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,804
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 packagist
35/35Publish recencylatest publish 60 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmicrosoft/microsoft-graph-core
ecosystemspackagist
any_deprecatedno
min_days_since_publish60

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests10 out of 19 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicsdevxeng
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

75Good · 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.2/2.5CI-Tests10 out of 19 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 9/11 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 14 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
5.2/7.5Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
0/5Packagingno data
0/5Pinned-Dependenciesno data
1.5/5SASTSAST tool is not run on all commits -- score normalized to 3
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_aggregate7.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

33At Risk · 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 configphpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/40 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes43,855
source_files_sampled40
oversized_source_files0

Key facts

16GitHub stars
32contributors
14commits, last 12 months
30days since last push
24releases
2bus factor
9open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-19 03:57 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests10 out of 19 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 9/11 approved changesets -- score normalized to 8
10Contributorsproject has 14 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
3SASTSAST tool is not run on all commits -- score normalized to 3
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistmicrosoft/kiota-authentication-phpleague^2.0.2composer.json
Packagistmicrosoft/kiota-http-guzzle^2.0.2composer.json
Packagistmicrosoft/kiota-serialization-json^2.0.2composer.json
Packagistmicrosoft/kiota-serialization-text^2.0.2composer.json
Packagistmicrosoft/kiota-serialization-form^2.0.2composer.json
Packagistmicrosoft/kiota-serialization-multipart^2.0.2composer.json
All dependencies 11

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

RegistryPackageVersionRelation
Packagistmicrosoft/kiota-authentication-phpleaguedirect
Packagistmicrosoft/kiota-http-guzzledirect
Packagistmicrosoft/kiota-serialization-formdirect
Packagistmicrosoft/kiota-serialization-jsondirect
Packagistmicrosoft/kiota-serialization-multipartdirect
Packagistmicrosoft/kiota-serialization-textdirect
Packagistext-jsonindirect
Packagistmikey179/vfsstreamindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
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.14.0 — full methodology · metrics wiki.

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