Software health reportschema 0.18.0 · metrics 2.10.0 · 2026-07-21 09:21 UTC

microsoft / azure-devops-extension-api

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

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

microsoft/azure-devops-extension-api holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Security (85/100) and lowest on AI Readiness (45/100). It was last updated 4 days ago. 3 contributors account for most of its recent work.

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.

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)

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

Ownership

MicrosoftOrganization

125,520 followers8,208 public repossince Dec 2013

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	azure-devops-extension-api	5.275.0	331,962	111	4 days ago	extensions azure-devops visual-studio-team-services

Metrics by category

Vitality

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

81Excellent · 21% of overall

Development activity

77Good

How it's scored

36/36	Push recency — last push 4 days ago
14.5/36	Commit cadence — 21/52 weeks with commits
16.5/18	Commit volume — 67 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 25 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	67
human_commit_share	—
days_since_last_push	4
active_weeks_last_year	21

Release discipline

88Excellent

How it's scored

16.2/27	Ships releases — 97 version tags (no GitHub releases)
36/36	Release recency — latest release 6 days ago
27/27	Release cadence — a release every ~14.6 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	97
latest_release_tag	5.275.0
releases_from_tags	yes
days_since_latest_release	6
mean_days_between_releases	14.6

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

Popularity & adoption

57Moderate

How it's scored

34/60	Stars — 125 stars
14.4/25	Forks — 54 forks
8.7/15	Watchers — 38 watchers

Inputs used

forks	54
stars	125
watchers	38
growth_state	organic
growth_factor_pct	100

Community health

65Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
13.5/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	—
has_contributing	no
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

92Excellent

How it's scored

73.6/80	Monthly downloads — 331,962 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	azure-devops-extension-api
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	331,962
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

Maintainer resilience (bus factor)

77Good

How it's scored

36/54	Bus factor — 3 contributor(s) cover half of all commits
17.3/22.5	Commit distribution — top contributor authored 23% of commits
13.5/13.5	Contributor breadth — 26 contributors
10/10	OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10

Inputs used

bus_factor	3
contributors_sampled	26
top_contributor_share	0.233

Issue & PR responsiveness

57Moderate

How it's scored

7.8/42	Issue resolution — 19% of issues closed
26.5/30	PR acceptance — 84/95 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15	OpenSSF Scorecard: Code-Review — all changesets reviewed

Inputs used

merged_prs	84
open_issues	83
closed_issues	19
prs_merged_7d	—
prs_decided_7d	—
prs_merged_30d	—
prs_decided_30d	—
issue_closed_ratio	0.186
closed_unmerged_prs	11
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.

Ownership & stewardship

100Exceptional

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain — verified-domain status not read for this organization
25/25	Owner reach — 125,520 followers of microsoft
25/25	Track record — 8,208 public repos, account ~12 yr old

Inputs used

followers	125,520
owner_type	Organization
is_verified	—
owner_login	microsoft
public_repos	8,208
account_age_days	4,605

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 4 days ago
20/20	Version history — 111 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	azure-devops-extension-api
ecosystems	npm
any_deprecated	no
min_days_since_publish	4

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall

Engineering practices

44Weak

How it's scored

0/24	CI workflows
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 13 out of 13 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

50Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

85Excellent · 16% of overall

Security posture

81Excellent

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5	Code-Review — all changesets reviewed
2.5/2.5	Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10	Dangerous-Workflow — no data
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 25 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
5/5	SAST — SAST tool is run on all commits
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
3/7.5	Vulnerabilities — 6 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	12
scorecard_version	v5.5.0
checks_inconclusive	6
scorecard_aggregate	8.1

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/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	6
affected_packages	2
assessed_packages	55
unassessed_packages	0
affected_by_severity	high 2
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 55 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.

45Weak · 4% of overall

Agent context & guidance

1Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
0/40	Legible commit history — no data

Inputs used

has_llms_txt	no
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.

Verify loop (build / test / typecheck)

60Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no data
0/8	Automated maintenance — no data
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	tsconfig.json
agent_commit_share	—
toolchain_manifests	—
dependency_bot_commit_share	—

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

95Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
50/55	Manageable file sizes — 13/142 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	184,944
source_files_sampled	142
oversized_source_files	13

Key facts

125GitHub stars

26contributors

67commits, last 12 months

4days since last push

97releases

3bus factor

83open issues

npmpackage ecosystems

Data collection warnings

deps.dev does not index npm:azure-devops-extension-api@5.275.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 125 ★ / 54 ⇿

125Stars

54Forks

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.

Each point covers 8 days.

OpenSSF Scorecard 8.1 / 10

8.1aggregate

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-21 09:20 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal 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
10	CI-Tests	13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
10	Code-Review	all changesets reviewed
10	Contributors	project has 3 contributing companies or organizations -- score normalized to 10
n/a	Dangerous-Workflow	no workflows found
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	25 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
10	SAST	SAST tool is run on all commits
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
4	Vulnerabilities	6 existing vulnerabilities detected

Direct dependencies 1

Registry	Package	Version constraint	Manifest
npm	whatwg-fetch	`~3.0.0`	package.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.

Registry	Package	Version	Relation
npm	whatwg-fetch	`3.0.0`	direct
npm	array-differ	`1.0.0`	indirect
npm	array-union	`1.0.2`	indirect
npm	array-uniq	`1.0.3`	indirect
npm	arrify	`1.0.1`	indirect
npm	asap	`2.0.6`	indirect
npm	azure-devops-extension-sdk	`4.0.2`	indirect
npm	balanced-match	`1.0.0`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	commander	`2.11.0`	indirect
npm	concat-map	`0.0.1`	indirect
npm	del	`2.2.2`	indirect
npm	emitter-mixin	`0.0.3`	indirect
npm	errno	`0.1.7`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	function-bind	`1.1.1`	indirect
npm	glob	`7.1.3`	indirect
npm	globby	`5.0.0`	indirect
npm	graceful-fs	`4.1.11`	indirect
npm	has	`1.0.3`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.3`	indirect
npm	interpret	`1.4.0`	indirect
npm	is-core-module	`2.8.1`	indirect
npm	is-path-cwd	`1.0.0`	indirect
npm	is-path-in-cwd	`1.0.1`	indirect
npm	is-path-inside	`1.0.1`	indirect
npm	junk	`1.0.3`	indirect
npm	maximatch	`0.1.0`	indirect
npm	minimatch	`3.1.2`	indirect
npm	minimist	`1.2.8`	indirect
npm	mkdirp	`0.5.6`	indirect
npm	node	`22.22.2`	indirect
npm	node-bin-setup	`1.0.6`	indirect
npm	object-assign	`4.1.1`	indirect
npm	once	`1.4.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-is-inside	`1.0.2`	indirect
npm	path-parse	`1.0.7`	indirect
npm	pify	`2.3.0`	indirect
npm	pinkie	`2.0.4`	indirect
npm	pinkie-promise	`2.0.1`	indirect
npm	promise	`7.3.1`	indirect
npm	prr	`1.0.1`	indirect
npm	rechoir	`0.6.2`	indirect
npm	recursive-copy	`2.0.9`	indirect
npm	resolve	`1.21.0`	indirect
npm	rimraf	`2.6.2`	indirect
npm	shelljs	`0.8.5`	indirect
npm	slash	`1.0.0`	indirect
npm	source-map	`0.6.1`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	typescript	`5.7.3`	indirect
npm	uglify-es	`3.1.10`	indirect
npm	wrappy	`1.0.2`	indirect

Dependency advisories 2

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

Package	Version	Relation	Severity	Advisories	Fixed in
brace-expansion	`1.1.11`	indirect	high	3	`5.0.7`
minimatch	`3.1.2`	indirect	high	3	`10.2.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.

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

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

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records