Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 08:29 UTC

pnp / cli-microsoft365-mcp-server

Manage Microsoft 365 using MCP server

TypeScriptMIT★ 131 stars⑂ 28 forkssince Apr 2025View on GitHub ↗
KindLibraryCommand-line toolMCP serverhow this is determined

pnp/cli-microsoft365-mcp-server holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (68/100) and lowest on Engineering Quality (32/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

1,905 followers125 public repossince Aug 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@pnp/cli-microsoft365-mcp-server0.1.244,1142435 days agomicrosoft365sharepointonlinemcpmodel-context-protocolai-assistantcli-for-microsoft-365

Metrics by category

Vitality

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

39Weak · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
4.2/36Commit cadence — 6/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
10/10OpenSSF Scorecard: Maintained — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year30
human_commit_share0.661
days_since_last_push4
active_weeks_last_year6
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

68Good · 17% of overall
How it's scored
34.3/60Stars — 131 stars
11.9/25Forks — 28 forks
6.4/15Watchers — 15 watchers
Inputs used
forks28
stars131
watchers15
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
48.2/80Monthly downloads — 4,114 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@pnp/cli-microsoft365-mcp-server
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads4,114
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
38.9/42Issue resolution — 92% of issues closed
12.4/30PR acceptance — 43/104 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs43
open_issues3
closed_issues37
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.925
closed_unmerged_prs61
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 backing — organization-owned
0/20Verified domain
23.6/25Owner reach — 1,905 followers of pnp
25/25Track record — 125 public repos, account ~9 yr old
Inputs used
followers1,905
owner_typeOrganization
is_verifiedno
owner_loginpnp
public_repos125
account_age_days3,321

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 35 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@pnp/cli-microsoft365-mcp-server
ecosystemsnpm
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

32At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 5 out of 19 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/@pnp/cli-microsoft365-mcp-server
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicsmcp, microsoft365, hacktoberfest
has_wikiyes
homepagehttps://www.npmjs.com/package/@pnp/cli-microsoft365-mcp-server
docs_sitehttps://www.npmjs.com/package/@pnp/cli-microsoft365-mcp-server
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.5/2.5CI-Tests — 5 out of 19 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/11 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, 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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages96
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:@pnp/cli-microsoft365-mcp-server@0.1.24 runtime dependency closure — what installing the published package pulls in — 96 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.9/40Legible commit history — 3 of 41 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.073
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 62
8/8Automated maintenance — 21 of the last 62 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.339
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes7,446
source_files_sampled2
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

131GitHub stars
1contributors
30commits, last 12 months
4days since last push
0releases
1bus factor
3open 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 ★ / 28 ⇿
0Stars
28Forks

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.

0510152025302832025-062026-012026-09

Each point covers 2 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-10-03 08:29 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
2CI-Tests5 out of 19 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/11 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@modelcontextprotocol/sdk1.30.0package.json
npmfuse.js7.5.0package.json
All dependencies 133

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

RegistryPackageVersionRelation
npm@modelcontextprotocol/sdk1.30.0direct
npmfuse.js7.5.0direct
npm@cspotcode/source-map-support0.8.1indirect
npm@hono/node-server1.19.17indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@tsconfig/node101.0.11indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.4indirect
npm@types/node26.3.0indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmaccepts2.0.0indirect
npmacorn8.15.0indirect
npmacorn-walk8.3.4indirect
npmajv8.18.0indirect
npmajv-formats3.0.1indirect
npmarg4.1.3indirect
npmbody-parser2.3.0indirect
npmbytes3.1.2indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmcontent-disposition1.0.1indirect
npmcontent-type1.0.5indirect
npmcontent-type2.0.0indirect
npmcookie0.7.2indirect
npmcookie-signature1.2.2indirect
npmcors2.8.5indirect
npmcreate-require1.1.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdepd2.0.0indirect
npmdiff4.0.2indirect
npmdunder-proto1.0.1indirect
npmee-first1.1.1indirect
npmencodeurl2.0.0indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.1indirect
npmescape-html1.0.3indirect
npmetag1.8.1indirect
npmeventsource3.0.7indirect
npmeventsource-parser3.0.3indirect
npmexpress5.2.1indirect
npmexpress-rate-limit8.5.1indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.6indirect
npmfinalhandler2.1.1indirect
npmforwarded0.2.0indirect
npmfresh2.0.0indirect
npmfunction-bind1.1.2indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmhas-symbols1.1.0indirect
npmhasown2.0.2indirect
npmhono4.13.5indirect
npmhttp-errors2.0.1indirect
npmiconv-lite0.7.2indirect
npminherits2.0.4indirect
npmip-address10.5.0indirect
npmipaddr.js1.9.1indirect
npmis-promise4.0.0indirect
npmisexe2.0.0indirect
npmjose6.1.3indirect
npmjson-schema-traverse1.0.0indirect
npmjson-schema-typed8.0.2indirect
npmmake-error1.3.6indirect
npmmath-intrinsics1.1.0indirect
npmmedia-typer1.1.0indirect
npmmerge-descriptors2.0.0indirect
npmmime-db1.54.0indirect
npmmime-types3.0.2indirect
npmms2.1.3indirect
npmnegotiator1.0.0indirect
npmobject-assign4.1.1indirect
npmobject-inspect1.13.4indirect
npmon-finished2.4.1indirect
npmonce1.4.0indirect
npmparseurl1.3.3indirect
npmpath-key3.1.1indirect
npmpath-to-regexp8.4.2indirect
npmpkce-challenge5.0.0indirect
npmproxy-addr2.0.7indirect
npmqs6.15.2indirect
npmrange-parser1.2.1indirect
npmraw-body3.0.2indirect
npmrequire-from-string2.0.2indirect
npmrouter2.2.0indirect
npmsafer-buffer2.1.2indirect
npmsend1.2.1indirect
npmserve-static2.2.1indirect
npmsetprototypeof1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.1.0indirect
npmside-channel-list1.0.0indirect
npmside-channel-map1.0.1indirect
npmside-channel-weakmap1.0.2indirect
npmstatuses2.0.2indirect
npmtoidentifier1.0.1indirect
npmts-node10.9.2indirect
npmtype-is2.1.0indirect
npmtypescript7.0.2indirect
npmundici-types8.3.0indirect
npmunpipe1.0.0indirect
npmv8-compile-cache-lib3.0.1indirect
npmvary1.1.2indirect
npmwhich2.0.2indirect
npmwrappy1.0.2indirect
npmyn3.1.1indirect
npmzod4.3.6indirect
npmzod-to-json-schema3.25.1indirect
Dependency advisories 0

Installing npm:@pnp/cli-microsoft365-mcp-server@0.1.24 pulls in 96 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.