Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 16:54 UTC

processout / processout-node

ProcessOut API bindings for node.js

TypeScriptMIT★ 4 stars⑂ 2 forkssince Jul 2015View on GitHub ↗

processout/processout-node holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (74/100) and lowest on Community & Adoption (39/100). It was last updated 14 days ago. 2 contributors account 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 56 is calibrated to 59 on the published index scale (record calibration 2026-08-02).

Ownership

ProcessOutOrganization · verified domain

26 followers44 public repossince Oct 2014

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	processout	11.0.1	9,279	116	32 days ago	processout api bindings

Metrics by category

Vitality

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

60Moderate · 21% of overall

Development activity

38Weak

How it's scored

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

Inputs used

commits_last_year	3
human_commit_share	1
days_since_last_push	14
active_weeks_last_year	2

Release discipline

92Excellent

How it's scored

27/27	Ships releases — 50 releases published
36/36	Release recency — latest release 32 days ago
19.8/27	Release cadence — a release every ~97.1 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	50
latest_release_tag	v11.0.1
releases_from_tags	no
days_since_latest_release	32
mean_days_between_releases	97.1

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?

39Weak · 17% of overall

Popularity & adoption

12Critical

How it's scored

7.7/60	Stars — 4 stars
0/25	Forks — 2 forks
4.3/15	Watchers — 7 watchers

Inputs used

forks	2
stars	4
watchers	7
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 (MIT)
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	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

66Good

How it's scored

52.9/80	Monthly downloads — 9,279 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	processout
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	9,279
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?

74Good · 23% of overall

Maintainer resilience (bus factor)

51Moderate

How it's scored

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

Inputs used

bus_factor	2
contributors_sampled	8
top_contributor_share	0.472

Issue & PR responsiveness

72Good

How it's scored

42/42	Issue resolution — 100% of issues closed
13.4/30	PR acceptance — 17/38 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15	OpenSSF Scorecard: Code-Review — Found 16/29 approved changesets -- score normalized to 5

Inputs used

merged_prs	17
open_issues	0
closed_issues	16
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	21
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

84Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
10.3/25	Owner reach — 26 followers of processout
24/25	Track record — 44 public repos, account ~11 yr old

Inputs used

followers	26
owner_type	Organization
is_verified	yes
owner_login	processout
public_repos	44
account_age_days	4,366

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	processout
ecosystems	npm
any_deprecated	no
min_days_since_publish	32

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall

Engineering practices

50Moderate

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
2/20	OpenSSF Scorecard: CI-Tests — 3 out of 16 merged PRs checked by a CI test -- score normalized to 1

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://docs.processout.com
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

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

46Weak · 16% of overall

Security posture

32At Risk

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
0.2/2.5	CI-Tests — 3 out of 16 merged PRs checked by a CI test -- score normalized to 1
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5	Code-Review — Found 16/29 approved changesets -- score normalized to 5
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
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
1.5/7.5	Maintained — 3 commit(s) and 0 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
1/5	SAST — SAST tool is not run on all commits -- score normalized to 2
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 — 11 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	3.2

Excluded from scoring (no data or not applicable): Branch-Protection, 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	6
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:processout@11.0.1 runtime dependency closure — what installing the published package pulls in — 6 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.

51Moderate · 4% of overall

Agent context & guidance

14Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.26
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

61Moderate

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — Dockerfile, lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
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	yes
typed_language	yes
bootstrap_files	Makefile
has_devcontainer	no
has_linter_config	no
typecheck_configs	tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Code legibility for models

99Exceptional

How it's scored

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

Inputs used

primary_language	TypeScript
largest_source_bytes	104,387
source_files_sampled	262
oversized_source_files	4

Key facts

4GitHub stars

8contributors

3commits, last 12 months

14days since last push

50releases

2bus 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 ★ / 2 ⇿

0Stars

2Forks

20Releases

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 1Minor 5Patch 14

Each point covers 4 days.

OpenSSF Scorecard 3.2 / 10

3.2aggregate

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-26 16:54 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
1	CI-Tests	3 out of 16 merged PRs checked by a CI test -- score normalized to 1
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
5	Code-Review	Found 16/29 approved changesets -- score normalized to 5
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
2	Maintained	3 commit(s) and 0 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
2	SAST	SAST tool is not run on all commits -- score normalized to 2
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	11 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
npm	@types/node	`^13.7.4`	package.json
npm	node-fetch	`^2.6.0`	package.json
npm	btoa	`^1.1.2`	package.json

All dependencies 176

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

Registry	Package	Version	Relation
npm	@types/node	`13.13.52`	direct
npm	btoa	`1.2.1`	direct
npm	node-fetch	`2.7.0`	direct
npm	ansi-colors	`3.2.3`	indirect
npm	ansi-regex	`3.0.1`	indirect
npm	ansi-regex	`4.1.1`	indirect
npm	ansi-styles	`3.2.1`	indirect
npm	argparse	`1.0.10`	indirect
npm	array-buffer-byte-length	`1.0.2`	indirect
npm	array.prototype.reduce	`1.0.8`	indirect
npm	arraybuffer.prototype.slice	`1.0.4`	indirect
npm	assertion-error	`1.1.0`	indirect
npm	async-function	`1.0.0`	indirect
npm	available-typed-arrays	`1.0.7`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	brace-expansion	`1.1.18`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	call-bind	`1.0.9`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	camelcase	`5.3.1`	indirect
npm	chai	`3.5.0`	indirect
npm	chalk	`2.4.2`	indirect
npm	cliui	`5.0.0`	indirect
npm	color-convert	`1.9.3`	indirect
npm	color-name	`1.1.3`	indirect
npm	concat-map	`0.0.1`	indirect
npm	data-view-buffer	`1.0.2`	indirect
npm	data-view-byte-length	`1.0.2`	indirect
npm	data-view-byte-offset	`1.0.1`	indirect
npm	debug	`3.2.6`	indirect
npm	decamelize	`1.2.0`	indirect
npm	deep-eql	`0.1.3`	indirect
npm	define-data-property	`1.1.4`	indirect
npm	define-properties	`1.2.1`	indirect
npm	diff	`3.5.0`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	emoji-regex	`7.0.3`	indirect
npm	es-abstract	`1.24.2`	indirect
npm	es-abstract-get	`1.0.0`	indirect
npm	es-array-method-boxes-properly	`1.0.0`	indirect
npm	es-define-property	`1.0.1`	indirect
npm	es-errors	`1.3.0`	indirect
npm	es-object-atoms	`1.1.2`	indirect
npm	es-set-tostringtag	`2.1.0`	indirect
npm	es-to-primitive	`1.3.4`	indirect
npm	escape-string-regexp	`1.0.5`	indirect
npm	esprima	`4.0.1`	indirect
npm	find-up	`3.0.0`	indirect
npm	flat	`4.1.1`	indirect
npm	for-each	`0.3.5`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	function.prototype.name	`1.2.0`	indirect
npm	functions-have-names	`1.2.3`	indirect
npm	generator-function	`2.0.1`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	get-symbol-description	`1.1.0`	indirect
npm	glob	`7.1.3`	indirect
npm	globalthis	`1.0.4`	indirect
npm	gopd	`1.2.0`	indirect
npm	growl	`1.10.5`	indirect
npm	has-bigints	`1.1.0`	indirect
npm	has-flag	`3.0.0`	indirect
npm	has-property-descriptors	`1.0.2`	indirect
npm	has-proto	`1.2.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hasown	`2.0.4`	indirect
npm	he	`1.2.0`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	internal-slot	`1.1.0`	indirect
npm	is-array-buffer	`3.0.5`	indirect
npm	is-async-function	`2.1.1`	indirect
npm	is-bigint	`1.1.0`	indirect
npm	is-boolean-object	`1.2.2`	indirect
npm	is-buffer	`2.0.5`	indirect
npm	is-callable	`1.2.7`	indirect
npm	is-data-view	`1.0.2`	indirect
npm	is-date-object	`1.1.0`	indirect
npm	is-document.all	`1.0.0`	indirect
npm	is-finalizationregistry	`1.1.1`	indirect
npm	is-fullwidth-code-point	`2.0.0`	indirect
npm	is-generator-function	`1.1.2`	indirect
npm	is-map	`2.0.3`	indirect
npm	is-negative-zero	`2.0.3`	indirect
npm	is-number-object	`1.1.1`	indirect
npm	is-regex	`1.2.1`	indirect
npm	is-set	`2.0.3`	indirect
npm	is-shared-array-buffer	`1.0.4`	indirect
npm	is-string	`1.1.1`	indirect
npm	is-symbol	`1.1.1`	indirect
npm	is-typed-array	`1.1.15`	indirect
npm	is-weakmap	`2.0.2`	indirect
npm	is-weakref	`1.1.1`	indirect
npm	is-weakset	`2.0.4`	indirect
npm	isarray	`2.0.5`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-yaml	`3.13.1`	indirect
npm	locate-path	`3.0.0`	indirect
npm	lodash	`4.18.1`	indirect
npm	log-symbols	`2.2.0`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	minimatch	`3.0.4`	indirect
npm	minimist	`1.2.8`	indirect
npm	mkdirp	`0.5.4`	indirect
npm	mocha	`6.2.3`	indirect
npm	ms	`2.1.1`	indirect
npm	node-environment-flags	`1.0.5`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	object-keys	`1.1.1`	indirect
npm	object.assign	`4.1.0`	indirect
npm	object.assign	`4.1.7`	indirect
npm	object.getownpropertydescriptors	`2.1.9`	indirect
npm	once	`1.4.0`	indirect
npm	own-keys	`1.0.2`	indirect
npm	p-limit	`2.3.0`	indirect
npm	p-locate	`3.0.0`	indirect
npm	p-try	`2.2.0`	indirect
npm	path-exists	`3.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	possible-typed-array-names	`1.1.0`	indirect
npm	reflect.getprototypeof	`1.0.10`	indirect
npm	regexp.prototype.flags	`1.5.4`	indirect
npm	require-directory	`2.1.1`	indirect
npm	require-main-filename	`2.0.0`	indirect
npm	safe-array-concat	`1.1.4`	indirect
npm	safe-push-apply	`1.0.0`	indirect
npm	safe-regex-test	`1.1.0`	indirect
npm	semver	`5.7.2`	indirect
npm	set-blocking	`2.0.0`	indirect
npm	set-function-length	`1.2.2`	indirect
npm	set-function-name	`2.0.2`	indirect
npm	set-proto	`1.0.0`	indirect
npm	side-channel	`1.1.1`	indirect
npm	side-channel-list	`1.0.1`	indirect
npm	side-channel-map	`1.0.1`	indirect
npm	side-channel-weakmap	`1.0.2`	indirect
npm	sprintf-js	`1.0.3`	indirect
npm	stop-iteration-iterator	`1.1.0`	indirect
npm	string-width	`2.1.1`	indirect
npm	string-width	`3.1.0`	indirect
npm	string.prototype.trim	`1.2.11`	indirect
npm	string.prototype.trimend	`1.0.10`	indirect
npm	string.prototype.trimstart	`1.0.8`	indirect
npm	strip-ansi	`4.0.0`	indirect
npm	strip-ansi	`5.2.0`	indirect
npm	strip-json-comments	`2.0.1`	indirect
npm	supports-color	`5.5.0`	indirect
npm	supports-color	`6.0.0`	indirect
npm	tr46	`0.0.3`	indirect
npm	type-detect	`0.1.1`	indirect
npm	type-detect	`1.0.0`	indirect
npm	typed-array-buffer	`1.0.3`	indirect
npm	typed-array-byte-length	`1.0.3`	indirect
npm	typed-array-byte-offset	`1.0.4`	indirect
npm	typed-array-length	`1.0.8`	indirect
npm	unbox-primitive	`1.1.0`	indirect
npm	webidl-conversions	`3.0.1`	indirect
npm	whatwg-url	`5.0.0`	indirect
npm	which	`1.3.1`	indirect
npm	which-boxed-primitive	`1.1.1`	indirect
npm	which-builtin-type	`1.2.1`	indirect
npm	which-collection	`1.0.2`	indirect
npm	which-module	`2.0.1`	indirect
npm	which-typed-array	`1.1.22`	indirect
npm	wide-align	`1.1.3`	indirect
npm	wrap-ansi	`5.1.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`4.0.3`	indirect
npm	yargs	`13.3.2`	indirect
npm	yargs-parser	`13.1.2`	indirect
npm	yargs-unparser	`1.6.0`	indirect

Dependency advisories 0

Installing npm:processout@11.0.1 pulls in 6 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