Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 23:12 UTC

microsoft / azure-pipelines-task-lib

Libraries for writing VSTS and TFS build tasks

TypeScript · PowerShellMIT★ 459 stars⑂ 282 forkssince Jul 2015View on GitHub ↗

microsoft/azure-pipelines-task-lib holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (89/100) and lowest on Vitality (45/100). It was last updated today. 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 74 is calibrated to 88 on the published index scale (record calibration 2026-08-02).

Ownership

MicrosoftOrganization · verified domain

129,649 followers8,301 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-pipelines-task-lib	5.279.0	113,894	97	33 days ago	azure-pipelines agent build release ci-cd task

Metrics by category

Vitality

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

45Weak · 21% of overall

Development activity

75Good

How it's scored

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

Inputs used

commits_last_year	38
human_commit_share	0.98
days_since_last_push	0
active_weeks_last_year	21

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

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?

84Excellent · 17% of overall

Popularity & adoption

75Good

How it's scored

43.2/60	Stars — 459 stars
20.4/25	Forks — 282 forks
11/15	Watchers — 98 watchers

Inputs used

forks	282
stars	459
watchers	98
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

93Exceptional

How it's scored

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

Inputs used

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

Ecosystem adoption (downloads)

84Excellent

How it's scored

67.4/80	Monthly downloads — 113,894 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	azure-pipelines-task-lib
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	113,894
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?

89Excellent · 23% of overall

Maintainer resilience (bus factor)

76Good

How it's scored

36/54	Bus factor — 3 contributor(s) cover half of all commits
16.1/22.5	Commit distribution — top contributor authored 28% of commits
13.5/13.5	Contributor breadth — 91 contributors
10/10	OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations

Inputs used

bus_factor	3
contributors_sampled	91
top_contributor_share	0.283

Issue & PR responsiveness

84Excellent

How it's scored

41.6/42	Issue resolution — 99% of issues closed
21.8/30	PR acceptance — 514/707 decided PRs merged
10.4/13	Newcomer PR acceptance — 4/5 first-time contributors' PRs merged in 30d
10.5/15	OpenSSF Scorecard: Code-Review — Found 22/28 approved changesets -- score normalized to 7

Inputs used

merged_prs	514
open_issues	4
closed_issues	397
prs_merged_7d	4
prs_decided_7d	5
prs_merged_30d	7
prs_decided_30d	9
issue_closed_ratio	0.99
closed_unmerged_prs	193
first_time_authors_30d	2
first_time_prs_merged_30d	4
first_time_prs_decided_30d	5

Ownership & stewardship

100Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
25/25	Owner reach — 129,649 followers of microsoft
25/25	Track record — 8,301 public repos, account ~12 yr old

Inputs used

followers	129,649
owner_type	Organization
is_verified	yes
owner_login	microsoft
public_repos	8,301
account_age_days	4,660

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	azure-pipelines-task-lib
ecosystems	npm
any_deprecated	no
min_days_since_publish	33

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall

Engineering practices

66Good

How it's scored

24/24	CI workflows — 3 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
18/20	OpenSSF Scorecard: CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

80Excellent

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — https://aka.ms/tfbuild
10/10	Repository description
0/10	Topics
0/10	Wiki

Inputs used

topics	—
has_wiki	no
homepage	https://aka.ms/tfbuild
docs_site	https://aka.ms/tfbuild
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

83Excellent · 16% of overall

Security posture

79Good

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
6/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5	CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5	Code-Review — Found 22/28 approved changesets -- score normalized to 7
2.5/2.5	Contributors — project has 12 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
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 — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
5/5	Pinned-Dependencies — all dependencies are pinned
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
6/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5	Vulnerabilities — 2 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	7.9

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	53
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:azure-pipelines-task-lib@5.279.0 runtime dependency closure — what installing the published package pulls in — 53 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.

75Good · 4% of overall

Agent context & guidance

40Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
40/40	Legible commit history — 94 of 98 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.959
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

84Excellent

How it's scored

12.6/18	One-command bootstrap — powershell/CompiledHelpers/VstsTaskSdk.csproj (toolchain convention, no task runner)
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — node/docs/tsconfig.json, node/test/tsconfig.json, node/tsconfig.json
10/10	Reproducible environment — lockfile
10/10	Demonstrated agent practice — 11 of the last 100 commits agent-authored or agent-credited
8/8	Automated maintenance — 1 of the last 100 commits are automated dependency updates
10/10	OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned

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	node/docs/tsconfig.json, node/test/tsconfig.json, node/tsconfig.json
agent_commit_share	0.11
toolchain_manifests	powershell/CompiledHelpers/VstsTaskSdk.csproj
dependency_bot_commit_share	0.01

Code legibility for models

97Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
51.8/55	Manageable file sizes — 4/68 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	100,316
source_files_sampled	68
oversized_source_files	4

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — samples

Inputs used

example_dirs	samples
has_mcp_signal	no
api_schema_files	—
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

459GitHub stars

91contributors

38commits, last 12 months

0days since last push

0releases

3bus factor

4open 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 ★ / 282 ⇿

0Stars

282Forks

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 11 days.

OpenSSF Scorecard 7.9 / 10

7.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-09-13 23:12 UTC

10	Binary-Artifacts	no binaries found in the repo
8	Branch-Protection	branch protection is not maximal on development and all release branches
9	CI-Tests	27 out of 30 merged PRs checked by a CI test -- score normalized to 9
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
7	Code-Review	Found 22/28 approved changesets -- score normalized to 7
10	Contributors	project has 12 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
10	Pinned-Dependencies	all dependencies are pinned
0	SAST	SAST tool is not run on all commits -- score normalized to 0
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
8	Token-Permissions	detected GitHub workflow tokens with excessive permissions
8	Vulnerabilities	2 existing vulnerabilities detected

Direct dependencies 6

Registry	Package	Version constraint	Manifest
npm	adm-zip	`^0.6.0`	node/package.json
npm	minimatch	`^3.1.5`	node/package.json
npm	nodejs-file-downloader	`^4.11.1`	node/package.json
npm	q	`^1.5.1`	node/package.json
npm	semver	`^5.7.2`	node/package.json
npm	shelljs	`^0.10.0`	node/package.json

All dependencies 139

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

Registry	Package	Version	Relation
npm	adm-zip	`0.6.0`	direct
npm	minimatch	`10.2.6`	direct
npm	minimatch	`3.1.5`	direct
npm	minimatch	`9.0.9`	direct
npm	nodejs-file-downloader	`4.13.0`	direct
npm	q	`1.5.1`	direct
npm	semver	`5.7.2`	direct
npm	shelljs	`0.10.0`	direct
npm	@isaacs/cliui	`8.0.2`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@pkgjs/parseargs	`0.11.0`	indirect
npm	@types/minimatch	`3.0.3`	indirect
npm	@types/mocha	`10.0.10`	indirect
npm	@types/node	`16.18.105`	indirect
npm	@types/node	`20.19.25`	indirect
npm	@types/q	`1.5.8`	indirect
npm	@types/semver	`7.5.8`	indirect
npm	@types/shelljs	`0.10.0`	indirect
npm	@types/shelljs	`0.8.17`	indirect
npm	agent-base	`6.0.2`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`1.1.18`	indirect
npm	brace-expansion	`2.1.4`	indirect
npm	brace-expansion	`5.0.9`	indirect
npm	braces	`3.0.3`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chokidar	`4.0.3`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	concat-map	`0.0.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.3.6`	indirect
npm	debug	`4.4.1`	indirect
npm	decamelize	`4.0.0`	indirect
npm	diff	`7.0.0`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	execa	`5.1.1`	indirect
npm	fast-glob	`3.3.3`	indirect
npm	fastq	`1.19.1`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	follow-redirects	`1.16.0`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-stream	`6.0.1`	indirect
npm	glob	`10.5.0`	indirect
npm	glob	`11.1.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	https-proxy-agent	`5.0.1`	indirect
npm	human-signals	`2.1.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-stream	`2.0.1`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jackspeak	`3.4.3`	indirect
npm	jackspeak	`4.1.1`	indirect
npm	js-yaml	`4.3.2`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	lru-cache	`11.2.2`	indirect
npm	merge-stream	`2.0.0`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.8`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	mimic-fn	`2.1.0`	indirect
npm	minipass	`7.1.2`	indirect
npm	mocha	`11.8.0`	indirect
npm	ms	`2.1.2`	indirect
npm	ms	`2.1.3`	indirect
npm	npm-run-path	`4.0.1`	indirect
npm	onetime	`5.1.2`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`1.11.1`	indirect
npm	path-scurry	`2.0.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`2.3.2`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	readdirp	`4.1.2`	indirect
npm	require-directory	`2.1.1`	indirect
npm	reusify	`1.1.0`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	sanitize-filename	`1.6.3`	indirect
npm	serialize-javascript	`7.0.5`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`3.0.7`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.1.2`	indirect
npm	strip-final-newline	`2.0.0`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	truncate-utf8-bytes	`1.0.2`	indirect
npm	typescript	`4.9.5`	indirect
npm	typescript	`5.9.3`	indirect
npm	undici-types	`6.21.0`	indirect
npm	utf8-byte-length	`1.0.5`	indirect
npm	which	`2.0.2`	indirect
npm	workerpool	`9.3.4`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`17.7.2`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:azure-pipelines-task-lib@5.279.0 pulls in 53 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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records