Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 12:50 UTC

superpoweredSDK / web-audio-javascript-webassembly-SDK-interactive-audio

🌐 Superpowered Web Audio JavaScript and WebAssembly SDK for modern web browsers. Allows developers to implement low-latency interactive audio features into web sites and web apps with a friendly Javascript API. https://superpowered.com

No license detected★ 178 stars⑂ 19 forkssince Sep 2019View on GitHub ↗

KindLibraryhow this is determined

#audio #webassembly #spatialization #time-stretch #wasm #javascript #javascript-library #web-audio #audioworklet #web-audio-module #web-audio-worklet #web-audio-api #web-audio-library #javascript-audio #javascript-audio-library #javascript-framework

superpoweredSDK/web-audio-javascript-webassembly-SDK-interactive-audio holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (64/100) and lowest on Vitality (17/100). It was last updated 40 days ago. A single contributor accounts for most of its recent work.

overall / 100

At Risk

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

Ownership

Superpowered Organization

51 followers4 public repossince Apr 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	@superpoweredsdk/web	2.8.2	3,559	13	40 days ago	superpowered audio

Metrics by category

Vitality

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

17Critical · 21% of overall

Development activity

27At Risk

How it's scored

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

Inputs used

commits_last_year	4
human_commit_share	1
days_since_last_push	40
active_weeks_last_year	4

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?

45Weak · 17% of overall

Popularity & adoption

54Moderate

How it's scored

36.5/60	Stars — 178 stars
10.5/25	Forks — 19 forks
7/15	Watchers — 19 watchers

Inputs used

forks	19
stars	178
watchers	19
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

25At Risk

How it's scored

22.5/22.5	README
0/22.5	License — no license file detected
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	no
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)

59Moderate

How it's scored

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

Inputs used

packages	@superpoweredsdk/web
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	3,559
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?

64Moderate · 23% of overall

Maintainer resilience (bus factor)

27At Risk

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	4
top_contributor_share	0.59

Issue & PR responsiveness

85Excellent

How it's scored

37.7/42	Issue resolution — 90% of issues closed
28.4/30	PR acceptance — 18/19 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 12/24 approved changesets -- score normalized to 5

Inputs used

merged_prs	18
open_issues	4
closed_issues	35
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.897
closed_unmerged_prs	1
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

59Moderate

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
12.3/25	Owner reach — 51 followers of superpoweredSDK
17.1/25	Track record — 4 public repos, account ~12 yr old

Inputs used

followers	51
owner_type	Organization
is_verified	no
owner_login	superpoweredSDK
public_repos	4
account_age_days	4,574

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	@superpoweredsdk/web
ecosystems	npm
any_deprecated	no
min_days_since_publish	40

Engineering Quality

Are baseline engineering and documentation practices in place?

31At Risk · 19% of overall

Engineering practices

1Critical

How it's scored

0/24	CI workflows
0/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 17 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	no
has_tests	no
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://docs.superpowered.com
10/10	Repository description
10/10	Topics — 16 topics
10/10	Wiki

Inputs used

topics	audio, webassembly, spatialization, time-stretch, wasm, javascript, javascript-library, web-audio, audioworklet, web-audio-module, web-audio-worklet, web-audio-api, web-audio-library, javascript-audio, javascript-audio-library, javascript-framework
has_wiki	yes
homepage	—
docs_site	https://docs.superpowered.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?

34At Risk · 16% of overall

Security posture

18Critical

How it's scored

6/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 17 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.8/7.5	Code-Review — Found 12/24 approved changesets -- score normalized to 5
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
0/2.5	License — license file not detected
0/7.5	Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
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 — no data
2.2/7.5	Vulnerabilities — 7 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	13
scorecard_version	v5.5.0
checks_inconclusive	5
scorecard_aggregate	1.8

Excluded from scoring (no data or not applicable): 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	7
affected_packages	4
assessed_packages	65
unassessed_packages	0
affected_by_severity	critical 1, high 1, moderate 1, low 1
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 65 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.

41Weak · 4% of overall

Agent context & guidance

34At Risk

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.64
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

11Critical

How it's scored

0/18	One-command bootstrap
0/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 50
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	no
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

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

74Good

How it's scored

0/45	Type-checkable code — primary language unknown
40.5/55	Manageable file sizes — 5/19 source files over 60KB

Inputs used

primary_language	—
largest_source_bytes	64,466
source_files_sampled	19
oversized_source_files	5

Excluded from scoring (no data or not applicable): Type-checkable code. Remaining weights renormalized.

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

178GitHub stars

4contributors

4commits, last 12 months

40days since last push

0releases

1bus factor

4open issues

npmpackage ecosystems

Data collection warnings

Language breakdown unavailable
Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 19 ⇿

0Stars

19Forks

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

OpenSSF Scorecard 1.8 / 10

1.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-10-19 12:50 UTC

8	Binary-Artifacts	binaries present in source code
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 17 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
5	Code-Review	Found 12/24 approved changesets -- score normalized to 5
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
0	License	license file not detected
0	Maintained	1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
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
n/a	Token-Permissions	No tokens found
3	Vulnerabilities	7 existing vulnerabilities detected

All dependencies 65

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

Registry	Package	Version	Relation
npm	accepts	`2.0.0`	indirect
npm	body-parser	`2.2.2`	indirect
npm	bytes	`3.1.2`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	content-disposition	`1.0.1`	indirect
npm	content-type	`1.0.5`	indirect
npm	cookie	`0.7.2`	indirect
npm	cookie-signature	`1.2.2`	indirect
npm	debug	`4.4.3`	indirect
npm	depd	`2.0.0`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	ee-first	`1.1.1`	indirect
npm	encodeurl	`2.0.0`	indirect
npm	es-define-property	`1.0.1`	indirect
npm	es-errors	`1.3.0`	indirect
npm	es-object-atoms	`1.1.1`	indirect
npm	escape-html	`1.0.3`	indirect
npm	etag	`1.8.1`	indirect
npm	express	`5.2.1`	indirect
npm	finalhandler	`2.1.1`	indirect
npm	forwarded	`0.2.0`	indirect
npm	fresh	`2.0.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	gopd	`1.2.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	hasown	`2.0.2`	indirect
npm	http-errors	`2.0.1`	indirect
npm	iconv-lite	`0.7.2`	indirect
npm	inherits	`2.0.4`	indirect
npm	ipaddr.js	`1.9.1`	indirect
npm	is-promise	`4.0.0`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	media-typer	`1.1.0`	indirect
npm	merge-descriptors	`2.0.0`	indirect
npm	mime-db	`1.54.0`	indirect
npm	mime-types	`3.0.2`	indirect
npm	ms	`2.1.3`	indirect
npm	negotiator	`1.0.0`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	on-finished	`2.4.1`	indirect
npm	once	`1.4.0`	indirect
npm	parseurl	`1.3.3`	indirect
npm	path-to-regexp	`8.3.0`	indirect
npm	proxy-addr	`2.0.7`	indirect
npm	qs	`6.15.0`	indirect
npm	range-parser	`1.2.1`	indirect
npm	raw-body	`3.0.2`	indirect
npm	router	`2.2.0`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	send	`1.2.1`	indirect
npm	serve-static	`2.2.1`	indirect
npm	setprototypeof	`1.2.0`	indirect
npm	side-channel	`1.1.0`	indirect
npm	side-channel-list	`1.0.0`	indirect
npm	side-channel-map	`1.0.1`	indirect
npm	side-channel-weakmap	`1.0.2`	indirect
npm	statuses	`2.0.2`	indirect
npm	toidentifier	`1.0.1`	indirect
npm	type-is	`2.0.1`	indirect
npm	unpipe	`1.0.0`	indirect
npm	vary	`1.1.2`	indirect
npm	wrappy	`1.0.2`	indirect

Dependency advisories 4

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

Package	Version	Relation	Severity	Advisories	Fixed in
proxy-addr	`2.0.7`	indirect	critical	1	`2.0.8`
path-to-regexp	`8.3.0`	indirect	high	2	`8.4.0`
qs	`6.15.0`	indirect	moderate	3	`6.16.0`
body-parser	`2.2.2`	indirect	low	1	`2.3.0`

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