Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 14:22 UTC

microsoft / azure-devops-extension-api

REST client libraries and contracts for Azure DevOps web extension developers.

TypeScriptMIT★ 126 stars⑂ 54 forkssince Oct 2018View on GitHub ↗

microsoft/azure-devops-extension-api holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (82/100) and lowest on Engineering Quality (52/100). It was last updated 30 days ago. 3 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

MicrosoftOrganization · verified domain
129,566 followers8,301 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmazure-devops-extension-api5.276.0364,23111230 days agoextensionsazure-devopsvisual-studio-team-services

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
28.8/36Push recency — last push 30 days ago
13.2/36Commit cadence — 19/52 weeks with commits
16.3/18Commit volume — 65 commits in the last year
6/10OpenSSF Scorecard: Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year65
human_commit_share1
days_since_last_push30
active_weeks_last_year19
How it's scored
16.2/27Ships releases — 98 version tags (no GitHub releases)
36/36Release recency — latest release 30 days ago
27/27Release cadence — a release every ~14.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count98
latest_release_tag5.276.0
releases_from_tagsyes
days_since_latest_release30
mean_days_between_releases14.9
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?

69Good · 17% of overall
How it's scored
34/60Stars — 126 stars
14.4/25Forks — 54 forks
8.7/15Watchers — 37 watchers
Inputs used
forks54
stars126
watchers37
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
74.2/80Monthly downloads — 364,231 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesazure-devops-extension-api
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads364,231
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 factor — 3 contributor(s) cover half of all commits
17.1/22.5Commit distribution — top contributor authored 24% of commits
13.5/13.5Contributor breadth — 24 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor3
contributors_sampled24
top_contributor_share0.24
How it's scored
7.8/42Issue resolution — 19% of issues closed
26.3/30PR acceptance — 85/97 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs85
open_issues83
closed_issues19
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.186
closed_unmerged_prs12
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
20/20Verified domain
25/25Owner reach — 129,566 followers of microsoft
25/25Track record — 8,301 public repos, account ~12 yr old
Inputs used
followers129,566
owner_typeOrganization
is_verifiedyes
owner_loginmicrosoft
public_repos8,301
account_age_days4,658

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 30 days ago
20/20Version history — 112 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesazure-devops-extension-api
ecosystemsnpm
any_deprecatedno
min_days_since_publish30

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.microsoft.com/en-us/azure/devops/integrate
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.microsoft.com/en-us/azure/devops/integrate
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

79Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
4.5/7.5Maintained — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
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
1.5/7.5Vulnerabilities — 8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate7.4
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_packages1
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:azure-devops-extension-api@5.276.0 runtime dependency closure — what installing the published package pulls in — 1 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
32.5/40Legible commit history — 61 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.61
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 checking — tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
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_share0.1
toolchain_manifests—
dependency_bot_commit_share0
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)
50/55Manageable file sizes — 13/142 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes186,214
source_files_sampled142
oversized_source_files13

Key facts

126GitHub stars
24contributors
65commits, last 12 months
30days since last push
98releases
3bus factor
83open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-05: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 126 stars today.

More detail

Star and fork history 125 ★ / 54 ⇿
125Stars
54Forks
97Releases

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.

Star history is shown as collected on 2026-07-05. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02550751001251254942018-112022-092026-08
Major 0Minor 81Patch 16

Each point covers 8 days.

OpenSSF Scorecard 7.4 / 10
7.4aggregate

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-09-12 14:21 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-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6
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
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmwhatwg-fetch~3.0.0package.json
All dependencies 55

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

RegistryPackageVersionRelation
npmwhatwg-fetch3.0.0direct
npmarray-differ1.0.0indirect
npmarray-union1.0.2indirect
npmarray-uniq1.0.3indirect
npmarrify1.0.1indirect
npmasap2.0.6indirect
npmazure-devops-extension-sdk4.0.2indirect
npmbalanced-match1.0.0indirect
npmbrace-expansion1.1.11indirect
npmcommander2.11.0indirect
npmconcat-map0.0.1indirect
npmdel2.2.2indirect
npmemitter-mixin0.0.3indirect
npmerrno0.1.7indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.1indirect
npmglob7.1.3indirect
npmglobby5.0.0indirect
npmgraceful-fs4.1.11indirect
npmhas1.0.3indirect
npminflight1.0.6indirect
npminherits2.0.3indirect
npminterpret1.4.0indirect
npmis-core-module2.8.1indirect
npmis-path-cwd1.0.0indirect
npmis-path-in-cwd1.0.1indirect
npmis-path-inside1.0.1indirect
npmjunk1.0.3indirect
npmmaximatch0.1.0indirect
npmminimatch3.1.2indirect
npmminimist1.2.8indirect
npmmkdirp0.5.6indirect
npmnode22.22.2indirect
npmnode-bin-setup1.0.6indirect
npmobject-assign4.1.1indirect
npmonce1.4.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-is-inside1.0.2indirect
npmpath-parse1.0.7indirect
npmpify2.3.0indirect
npmpinkie2.0.4indirect
npmpinkie-promise2.0.1indirect
npmpromise7.3.1indirect
npmprr1.0.1indirect
npmrechoir0.6.2indirect
npmrecursive-copy2.0.9indirect
npmresolve1.21.0indirect
npmrimraf2.6.2indirect
npmshelljs0.8.5indirect
npmslash1.0.0indirect
npmsource-map0.6.1indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtypescript5.7.3indirect
npmuglify-es3.1.10indirect
npmwrappy1.0.2indirect
Dependency advisories 0

Installing npm:azure-devops-extension-api@5.276.0 pulls in 1 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.