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

biowasm / aioli

Framework for building fast genomics web tools with WebAssembly and WebWorkers

JavaScriptMIT★ 121 stars⑂ 14 forkssince Oct 2018View on GitHub ↗

KindLibraryWeb interfacehow this is determined

#genomics #webapp #webworkers #webassembly #wasm #javascript #bioinformatics

biowasm/aioli holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (65/100) and lowest on AI Readiness (39/100). It was last updated 13 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 55 is calibrated to 57 on the published index scale (record calibration 2026-08-02).

Ownership

biowasmOrganization · verified domain

14 followers2 public repossince Mar 2020

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
npm	@biowasm/aioli	3.2.3	7,768	27	56 days ago

Metrics by category

Vitality

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

57Moderate · 21% of overall

Development activity

39Weak

How it's scored

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

Inputs used

commits_last_year	3
human_commit_share	0.94
days_since_last_push	13
active_weeks_last_year	2

Release discipline

84Excellent

How it's scored

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

Inputs used

releases_count	22
latest_release_tag	v3.2.3
releases_from_tags	no
days_since_latest_release	56
mean_days_between_releases	199.7

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?

52Moderate · 17% of overall

Popularity & adoption

45Weak

How it's scored

33.7/60	Stars — 121 stars
9.3/25	Forks — 14 forks
1.7/15	Watchers — 3 watchers

Inputs used

forks	14
stars	121
watchers	3
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	2
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)

65Good

How it's scored

51.9/80	Monthly downloads — 7,768 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@biowasm/aioli
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	7,768
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?

65Good · 23% of overall

Maintainer resilience (bus factor)

25At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5	Commit distribution — top contributor authored 96% of commits
5.4/13.5	Contributor breadth — 4 contributors
10/10	OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	4
top_contributor_share	0.958

Issue & PR responsiveness

75Good

How it's scored

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

Inputs used

merged_prs	29
open_issues	0
closed_issues	21
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

74Good

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
8.5/25	Owner reach — 14 followers of biowasm
15.5/25	Track record — 2 public repos, account ~6 yr old

Inputs used

followers	14
owner_type	Organization
is_verified	yes
owner_login	biowasm
public_repos	2
account_age_days	2,366

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	@biowasm/aioli
ecosystems	npm
any_deprecated	no
min_days_since_publish	56

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 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 9 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

50Moderate

How it's scored

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

Inputs used

topics	genomics, webapp, webworkers, webassembly, wasm, javascript, bioinformatics
has_wiki	no
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?

54Moderate · 16% of overall

Security posture

43Weak

How it's scored

4.5/7.5	Binary-Artifacts — binaries present in source code
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 9 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
3/7.5	Code-Review — Found 5/12 approved changesets -- score normalized to 4
2.5/2.5	Contributors — project has 5 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
2.2/7.5	Maintained — 3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
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
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

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

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	2
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:@biowasm/aioli@3.2.3 runtime dependency closure — what installing the published package pulls in — 2 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.

39Weak · 4% of overall

Agent context & guidance

8Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.149
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 100
8/8	Automated maintenance — 6 of the last 100 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.06

Code legibility for models

39Weak

How it's scored

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

Inputs used

primary_language	JavaScript
largest_source_bytes	171,912
source_files_sampled	14
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 — examples

Inputs used

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

121GitHub stars

4contributors

3commits, last 12 months

13days since last push

22releases

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 ★ / 14 ⇿

0Stars

14Forks

21Releases

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 3Minor 11Patch 7

Each point covers 7 days.

OpenSSF Scorecard 4.3 / 10

4.3aggregate

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

6	Binary-Artifacts	binaries present in source code
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 9 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
4	Code-Review	Found 5/12 approved changesets -- score normalized to 4
10	Contributors	project has 5 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
3	Maintained	3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
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
10	Vulnerabilities	0 existing vulnerabilities detected

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	comlink	`^4.3.1`	package.json
npm	wasm-feature-detect	`^1.2.11`	package.json

All dependencies 211

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

Registry	Package	Version	Relation
npm	comlink	`4.3.1`	direct
npm	wasm-feature-detect	`1.2.11`	direct
npm	@cypress/request	`4.0.1`	indirect
npm	@cypress/xvfb	`1.2.4`	indirect
npm	@oxc-project/types	`0.147.0`	indirect
npm	@rolldown/binding-android-arm-eabi	`1.2.6`	indirect
npm	@rolldown/binding-android-arm64	`1.2.6`	indirect
npm	@rolldown/binding-darwin-arm64	`1.2.6`	indirect
npm	@rolldown/binding-darwin-x64	`1.2.6`	indirect
npm	@rolldown/binding-freebsd-x64	`1.2.6`	indirect
npm	@rolldown/binding-linux-arm-gnueabihf	`1.2.6`	indirect
npm	@rolldown/binding-linux-arm64-gnu	`1.2.6`	indirect
npm	@rolldown/binding-linux-arm64-musl	`1.2.6`	indirect
npm	@rolldown/binding-linux-ppc64-gnu	`1.2.6`	indirect
npm	@rolldown/binding-linux-s390x-gnu	`1.2.6`	indirect
npm	@rolldown/binding-linux-x64-gnu	`1.2.6`	indirect
npm	@rolldown/binding-linux-x64-musl	`1.2.6`	indirect
npm	@rolldown/binding-openharmony-arm64	`1.2.6`	indirect
npm	@rolldown/binding-win32-arm64-msvc	`1.2.6`	indirect
npm	@rolldown/binding-win32-x64-msvc	`1.2.6`	indirect
npm	@rolldown/pluginutils	`1.0.1`	indirect
npm	@types/sinonjs__fake-timers	`8.1.1`	indirect
npm	@types/sizzle	`2.3.3`	indirect
npm	@types/tmp	`0.2.6`	indirect
npm	ansi-escapes	`7.3.0`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.3.0`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	arch	`3.0.0`	indirect
npm	asn1	`0.2.6`	indirect
npm	assert-plus	`1.0.0`	indirect
npm	asynckit	`0.4.0`	indirect
npm	at-least-node	`1.0.0`	indirect
npm	aws-sign2	`0.7.0`	indirect
npm	aws4	`1.13.2`	indirect
npm	base64-js	`1.5.1`	indirect
npm	bcrypt-pbkdf	`1.0.2`	indirect
npm	blob-util	`2.0.2`	indirect
npm	bluebird	`3.7.2`	indirect
npm	buffer	`5.7.1`	indirect
npm	cachedir	`2.4.0`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	caseless	`0.12.0`	indirect
npm	chalk	`4.1.1`	indirect
npm	chrome-remote-interface	`0.33.3`	indirect
npm	ci-info	`4.4.0`	indirect
npm	cli-cursor	`5.0.0`	indirect
npm	cli-table3	`0.6.1`	indirect
npm	cli-truncate	`5.2.0`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	colorette	`2.0.20`	indirect
npm	colors	`1.4.0`	indirect
npm	combined-stream	`1.0.8`	indirect
npm	commander	`2.11.0`	indirect
npm	commander	`6.2.1`	indirect
npm	common-tags	`1.8.0`	indirect
npm	core-util-is	`1.0.2`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	cypress	`15.21.1`	indirect
npm	dashdash	`1.14.1`	indirect
npm	dayjs	`1.10.6`	indirect
npm	debug	`3.2.7`	indirect
npm	debug	`4.4.3`	indirect
npm	delayed-stream	`1.0.0`	indirect
npm	detect-libc	`2.1.2`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	ecc-jsbn	`0.1.2`	indirect
npm	emoji-regex	`10.6.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	end-of-stream	`1.4.4`	indirect
npm	environment	`1.1.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	eventemitter2	`6.4.7`	indirect
npm	eventemitter3	`5.0.4`	indirect
npm	execa	`4.1.0`	indirect
npm	executable	`4.1.1`	indirect
npm	extend	`3.0.2`	indirect
npm	extsprintf	`1.3.0`	indirect
npm	fdir	`6.5.0`	indirect
npm	forever-agent	`0.6.1`	indirect
npm	form-data	`4.0.6`	indirect
npm	fs-extra	`9.1.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-east-asian-width	`1.6.0`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	get-stream	`5.2.0`	indirect
npm	getpass	`0.1.7`	indirect
npm	global-dirs	`3.0.0`	indirect
npm	gopd	`1.2.0`	indirect
npm	graceful-fs	`4.2.6`	indirect
npm	has-flag	`4.0.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hasha	`5.2.2`	indirect
npm	hasown	`2.0.4`	indirect
npm	http-signature	`1.4.0`	indirect
npm	human-signals	`1.1.1`	indirect
npm	ieee754	`1.2.1`	indirect
npm	ini	`2.0.0`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-fullwidth-code-point	`5.1.0`	indirect
npm	is-installed-globally	`0.4.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-stream	`2.0.0`	indirect
npm	is-typedarray	`1.0.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	isstream	`0.1.2`	indirect
npm	jsbn	`0.1.1`	indirect
npm	json-schema	`0.4.0`	indirect
npm	json-stringify-safe	`5.0.1`	indirect
npm	jsonfile	`6.1.0`	indirect
npm	jsprim	`2.0.2`	indirect
npm	lightningcss	`1.33.0`	indirect
npm	lightningcss-android-arm64	`1.33.0`	indirect
npm	lightningcss-darwin-arm64	`1.33.0`	indirect
npm	lightningcss-darwin-x64	`1.33.0`	indirect
npm	lightningcss-freebsd-x64	`1.33.0`	indirect
npm	lightningcss-linux-arm-gnueabihf	`1.33.0`	indirect
npm	lightningcss-linux-arm64-gnu	`1.33.0`	indirect
npm	lightningcss-linux-arm64-musl	`1.33.0`	indirect
npm	lightningcss-linux-x64-gnu	`1.33.0`	indirect
npm	lightningcss-linux-x64-musl	`1.33.0`	indirect
npm	lightningcss-win32-arm64-msvc	`1.33.0`	indirect
npm	lightningcss-win32-x64-msvc	`1.33.0`	indirect
npm	listr2	`9.0.5`	indirect
npm	lodash	`4.18.1`	indirect
npm	lodash.once	`4.1.1`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	log-update	`6.1.0`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	merge-stream	`2.0.0`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	mimic-fn	`2.1.0`	indirect
npm	mimic-function	`5.0.1`	indirect
npm	minimist	`1.2.8`	indirect
npm	ms	`2.1.3`	indirect
npm	nanoid	`3.3.18`	indirect
npm	npm-run-path	`4.0.1`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	once	`1.4.0`	indirect
npm	onetime	`5.1.2`	indirect
npm	onetime	`7.0.0`	indirect
npm	ospath	`1.2.2`	indirect
npm	path-key	`3.1.1`	indirect
npm	pend	`1.2.0`	indirect
npm	performance-now	`2.1.0`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.7`	indirect
npm	pify	`2.3.0`	indirect
npm	postcss	`8.5.26`	indirect
npm	pretty-bytes	`5.6.0`	indirect
npm	process	`0.11.10`	indirect
npm	proxy-from-env	`1.0.0`	indirect
npm	pump	`3.0.0`	indirect
npm	qs	`6.16.0`	indirect
npm	request-progress	`3.0.0`	indirect
npm	restore-cursor	`5.1.0`	indirect
npm	rfdc	`1.4.1`	indirect
npm	rolldown	`1.2.6`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.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	signal-exit	`3.0.3`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	slice-ansi	`7.1.2`	indirect
npm	slice-ansi	`8.0.0`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	sshpk	`1.18.0`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`7.2.0`	indirect
npm	string-width	`8.2.2`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	strip-final-newline	`2.0.0`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	systeminformation	`5.33.6`	indirect
npm	throttleit	`1.0.0`	indirect
npm	tinyglobby	`0.2.17`	indirect
npm	tldts	`6.1.86`	indirect
npm	tldts-core	`6.1.86`	indirect
npm	tmp	`0.2.7`	indirect
npm	tough-cookie	`5.1.2`	indirect
npm	tree-kill	`1.2.2`	indirect
npm	tunnel-agent	`0.6.0`	indirect
npm	tweetnacl	`0.14.5`	indirect
npm	type-fest	`0.8.1`	indirect
npm	universalify	`2.0.0`	indirect
npm	untildify	`4.0.0`	indirect
npm	verror	`1.10.0`	indirect
npm	vite	`8.2.2`	indirect
npm	which	`2.0.2`	indirect
npm	wrap-ansi	`9.0.2`	indirect
npm	wrappy	`1.0.2`	indirect
npm	ws	`7.5.13`	indirect
npm	yauzl	`3.4.0`	indirect

Dependency advisories 0

Installing npm:@biowasm/aioli@3.2.3 pulls in 2 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