Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 08:49 UTC

upwork / node-upwork-oauth2

Node.JS bindings for Upwork API (OAuth2)

JavaScriptApache-2.0★ 13 stars⑂ 8 forkssince Nov 2018View on GitHub ↗

upwork/node-upwork-oauth2 holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (66/100) and lowest on Security (40/100). It was last updated 29 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

UpworkOrganization · verified domain

320 followers28 public repossince Mar 2015

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	@upwork/node-upwork-oauth2	2.3.1	3,628	14	29 days ago	oauth2 rest upwork api wrapper

Metrics by category

Vitality

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

55Moderate · 21% of overall

Development activity

36Weak

How it's scored

28.8/36	Push recency — last push 29 days ago
0.7/36	Commit cadence — 1/52 weeks with commits
4.3/18	Commit volume — 2 commits in the last year
2/10	OpenSSF Scorecard: Maintained — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2

Inputs used

commits_last_year	2
human_commit_share	0.875
days_since_last_push	29
active_weeks_last_year	1

Release discipline

84Excellent

How it's scored

27/27	Ships releases — 12 releases published
36/36	Release recency — latest release 29 days ago
12.6/27	Release cadence — a release every ~307.6 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	12
latest_release_tag	v2.3.1
releases_from_tags	no
days_since_latest_release	29
mean_days_between_releases	307.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?

45Weak · 17% of overall

Popularity & adoption

32At Risk

How it's scored

17.5/60	Stars — 13 stars
7/25	Forks — 8 forks
7.9/15	Watchers — 27 watchers

Inputs used

forks	8
stars	13
watchers	27
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (Apache-2.0)
0/18	CONTRIBUTING guide
0/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	4
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

59Moderate

How it's scored

47.5/80	Monthly downloads — 3,628 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@upwork/node-upwork-oauth2
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	3,628
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?

66Good · 23% of overall

Maintainer resilience (bus factor)

13Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

76Good

How it's scored

42/42	Issue resolution — 100% of issues closed
22.8/30	PR acceptance — 19/25 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15	OpenSSF Scorecard: Code-Review — Found 1/10 approved changesets -- score normalized to 1

Inputs used

merged_prs	19
open_issues	0
closed_issues	7
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	1
prs_decided_30d	1
issue_closed_ratio	1
closed_unmerged_prs	6
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

91Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
18/25	Owner reach — 320 followers of upwork
22.6/25	Track record — 28 public repos, account ~11 yr old

Inputs used

followers	320
owner_type	Organization
is_verified	yes
owner_login	upwork
public_repos	28
account_age_days	4,190

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	@upwork/node-upwork-oauth2
ecosystems	npm
any_deprecated	no
min_days_since_publish	29

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall

Engineering practices

48Weak

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://developers.upwork.com
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	https://developers.upwork.com
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?

40Weak · 16% of overall

Security posture

38Weak

How it's scored

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

Inputs used

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

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

46Weak

How it's scored

17.9/35	Direct dependencies free of known advisories — 1 affected: request 2.88.2 (moderate 6.1)
6.7/25	Indirect dependencies free of known advisories — 4 affected: form-data 2.3.3 (high 7.5), uuid 3.4.0 (high 7.5), qs 6.5.5 (moderate 5.3), +1 more
21.9/40	No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,283 days ago

Inputs used

source	osv
advisories	7
affected_packages	5
assessed_packages	62
unassessed_packages	0
affected_by_severity	high 2, moderate 3
direct_affected_packages	1

Matched the npm:@upwork/node-upwork-oauth2@2.3.1 runtime dependency closure — what installing the published package pulls in — 62 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.

48Weak · 4% of overall

Agent context & guidance

29At Risk

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.551
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

40Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 56
8/8	Automated maintenance — 7 of the last 56 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

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

Code legibility for models

55Moderate

How it's scored

0/45	Type-checkable code — JavaScript without a type-check config
55/55	Manageable file sizes — 0/42 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	7,642
source_files_sampled	42
oversized_source_files	0

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 — example

Inputs used

example_dirs	example
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

13GitHub stars

1contributors

2commits, last 12 months

29days since last push

12releases

1bus factor

0open 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 ★ / 8 ⇿

0Stars

8Forks

6Releases

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.

Major 0Minor 2Patch 4

Each point covers 6 days.

OpenSSF Scorecard 3.8 / 10

3.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-09-20 08:49 UTC

10	Binary-Artifacts	no binaries found in the repo
6	Branch-Protection	branch protection is not maximal on development and all release branches
0	CI-Tests	0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
1	Code-Review	Found 1/10 approved changesets -- score normalized to 1
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
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
2	Maintained	2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	37 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
npm	pkginfo	`*`	package.json
npm	request	`2.88.2`	package.json
npm	simple-oauth2	`5.0.0`	package.json

All dependencies 138

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

Registry	Package	Version	Relation
npm	pkginfo	`0.4.1`	direct
npm	request	`2.88.2`	direct
npm	simple-oauth2	`5.0.0`	direct
npm	@hapi/boom	`10.0.1`	indirect
npm	@hapi/bourne	`3.0.0`	indirect
npm	@hapi/hoek	`10.0.1`	indirect
npm	@hapi/hoek	`11.0.2`	indirect
npm	@hapi/hoek	`9.3.0`	indirect
npm	@hapi/topo	`5.1.0`	indirect
npm	@hapi/wreck	`18.0.1`	indirect
npm	@sideway/address	`4.1.4`	indirect
npm	@sideway/formula	`3.0.1`	indirect
npm	@sideway/pinpoint	`2.0.0`	indirect
npm	ajv	`6.12.6`	indirect
npm	ansi-colors	`4.1.1`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	asn1	`0.2.6`	indirect
npm	assert-plus	`1.0.0`	indirect
npm	asynckit	`0.4.0`	indirect
npm	aws-sign2	`0.7.0`	indirect
npm	aws4	`1.12.0`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	bcrypt-pbkdf	`1.0.2`	indirect
npm	binary-extensions	`2.2.0`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	brace-expansion	`2.0.1`	indirect
npm	braces	`3.0.2`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	camelcase	`6.3.0`	indirect
npm	caseless	`0.12.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chokidar	`3.5.3`	indirect
npm	cliui	`7.0.4`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	combined-stream	`1.0.8`	indirect
npm	concat-map	`0.0.1`	indirect
npm	core-util-is	`1.0.2`	indirect
npm	dashdash	`1.14.1`	indirect
npm	debug	`4.3.4`	indirect
npm	decamelize	`4.0.0`	indirect
npm	delayed-stream	`1.0.0`	indirect
npm	diff	`5.0.0`	indirect
npm	ecc-jsbn	`0.1.2`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	escalade	`3.1.1`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	extend	`3.0.2`	indirect
npm	extsprintf	`1.3.0`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fill-range	`7.0.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	forever-agent	`0.6.1`	indirect
npm	form-data	`2.3.3`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.2`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	getpass	`0.1.7`	indirect
npm	glob	`7.2.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	har-schema	`2.0.0`	indirect
npm	har-validator	`5.1.5`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	http-signature	`1.2.0`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-binary-path	`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-plain-obj	`2.1.0`	indirect
npm	is-typedarray	`1.0.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isstream	`0.1.2`	indirect
npm	joi	`17.9.2`	indirect
npm	js-yaml	`4.1.0`	indirect
npm	jsbn	`0.1.1`	indirect
npm	json-schema	`0.4.0`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stringify-safe	`5.0.1`	indirect
npm	jsprim	`1.4.2`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	minimatch	`3.1.2`	indirect
npm	minimatch	`5.0.1`	indirect
npm	mocha	`10.2.0`	indirect
npm	ms	`2.1.2`	indirect
npm	ms	`2.1.3`	indirect
npm	nanoid	`3.3.3`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	oauth-sign	`0.9.0`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	performance-now	`2.1.0`	indirect
npm	picomatch	`2.3.1`	indirect
npm	psl	`1.9.0`	indirect
npm	punycode	`2.3.0`	indirect
npm	qs	`6.5.3`	indirect
npm	randombytes	`2.1.0`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	serialize-javascript	`6.0.0`	indirect
npm	sshpk	`1.17.0`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	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	tough-cookie	`2.5.0`	indirect
npm	tunnel-agent	`0.6.0`	indirect
npm	tweetnacl	`0.14.5`	indirect
npm	uri-js	`4.4.1`	indirect
npm	uuid	`3.4.0`	indirect
npm	verror	`1.10.0`	indirect
npm	workerpool	`6.2.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs-parser	`20.2.4`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 5

Installing npm:@upwork/node-upwork-oauth2@2.3.1 pulls in 62 packages, direct and transitive: 5 carry known advisories, of which 1 are direct dependencies.

Package	Version	Relation	Severity	Advisories	Fixed in
form-data	`2.3.3`	indirect	high	2	`4.0.6`
uuid	`3.4.0`	indirect	high	1	`13.0.1`
request	`2.88.2`	direct	moderate	1	`3.0.0`
qs	`6.5.5`	indirect	moderate	2	`6.16.0`
tough-cookie	`2.5.0`	indirect	moderate	1	`4.1.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.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