Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 11:38 UTC

wilzbach / msa

Modular BioJS compoment for a multiple sequence alignment

JavaScriptBSL-1.0★ 171 stars⑂ 80 forkssince May 2014archivedView on GitHub ↗

wilzbach/msa holds a health index of 14 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (60/100) and lowest on Vitality (17/100). The repository is archived, so no further maintenance is expected.

14
overall / 100
Critical

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.

14
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)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

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

Ownership

Sebastian WilzbachPersonal account
230 followers266 public repossince May 2013

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmsa1.0.3822483705 days agobiobiologicalbiojsgalaxy-vismsamultiplesequencealignmentfastaclustal

Metrics by category

Vitality

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

17Critical · 21% of overall
How it's scored
0/36Push recency — last push 1,570 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push1,570
active_weeks_last_year0
How it's scored
27/27Ships releases — 1 releases published
0/36Release recency — latest release 3,751 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count1
latest_release_tagv1.0.0
releases_from_tagsno
days_since_latest_release3,751
mean_days_between_releases—

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

52Moderate · 17% of overall
How it's scored
36.2/60Stars — 171 stars
15.8/25Forks — 80 forks
3.9/15Watchers — 6 watchers
Inputs used
forks80
stars171
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSL-1.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io, travis-ci.org
has_pull_request_templateno
How it's scored
38.9/80Monthly downloads — 822 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmsa
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads822
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.2/22.5Commit distribution — top contributor authored 95% of commits
12.2/13.5Contributor breadth — 9 contributors
10/10OpenSSF Scorecard: Contributors — project has 24 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.948
How it's scored
42/42Issue resolution — 100% of issues closed
27.2/30PR acceptance — 59/65 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 5/17 approved changesets -- score normalized to 2
Inputs used
merged_prs59
open_issues0
closed_issues195
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs6
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
17/25Owner reach — 230 followers of wilzbach
25/25Track record — 266 public repos, account ~13 yr old
Inputs used
followers230
owner_typeUser
is_verified—
owner_loginwilzbach
public_repos266
account_age_days4,872
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 3,705 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmsa
ecosystemsnpm
any_deprecatedno
min_days_since_publish3,705

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 12 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://msa.biojs.net
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttp://msa.biojs.net
docs_sitehttp://msa.biojs.net
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 12 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 5/17 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 24 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — project is archived
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.9
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Token-Permissions. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
6.1/25Indirect dependencies free of known advisories — 5 affected: form-data 2.3.3 (high 7.5), uuid 3.4.0 (high 7.5), qs 6.5.5 (moderate 5.3), +2 more
21.9/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,272 days ago
Inputs used
sourceosv
advisories7
affected_packages5
assessed_packages79
unassessed_packages0
affected_by_severityhigh 2, moderate 3
direct_affected_packages0
Matched the npm:msa@1.0.3 runtime dependency closure — what installing the published package pulls in — 79 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29.3/40Legible commit history — 55 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.55
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/86 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes12,525
source_files_sampled86
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — samples
Inputs used
example_dirssamples
has_mcp_signalno
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

171GitHub stars
9contributors
0commits, last 12 months
1,570days since last push
1releases
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 ★ / 80 ⇿
0Stars
80Forks
1Releases

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.

01325385063757532014-092019-112025-01
Major 1Minor 0Patch 0

Each point covers 10 days.

OpenSSF Scorecard 2.9 / 10
2.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-09 11:38 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
0CI-Tests0 out of 12 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/17 approved changesets -- score normalized to 2
10Contributorsproject has 24 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
npmbackbone-childs^1.0.3package.json
npmbackbone-thin^1.0.8package.json
npmbackbone-viewj^1.0.1package.json
npmbio.iohttps://github.com/wilzbach/bio.io.git#233c569a000b4e481bc682dc1c5024aaa8f4c3b6package.json
npmbiojs-events^0.0.4package.json
npmbiojs-model^0.0.2package.json
npmbiojs-vis-seqlogo0.0.14package.json
npmblueimp_canvastoblob^1.0.0package.json
npmbrowser-saveas^1.0.1package.json
npmdom-helper^1.0.0package.json
npmjbone^1.1.2package.json
npmkoala-js^1.0.7package.json
npmlinear-scale0.0.1package.json
npmlodash^4.13.1package.json
npmmouse-pos^1.0.3package.json
npmmsa-colorschemes^1.0.10package.json
npmstat.seqs^0.1.21package.json
npmxhr^2.2.0package.json
All dependencies 46

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

RegistryPackageVersionRelation
npmbackbone-childs^1.0.3direct
npmbackbone-thin^1.0.8direct
npmbackbone-viewj^1.0.1direct
npmbiojs-events^0.0.4direct
npmbiojs-model^0.0.2direct
npmbiojs-vis-seqlogo0.0.14direct
npmblueimp_canvastoblob^1.0.0direct
npmbrowser-saveas^1.0.1direct
npmdom-helper^1.0.0direct
npmjbone^1.1.2direct
npmkoala-js^1.0.7direct
npmlinear-scale0.0.1direct
npmlodash^4.13.1direct
npmmouse-pos^1.0.3direct
npmmsa-colorschemes^1.0.10direct
npmstat.seqs^0.1.21direct
npmxhr^2.2.0direct
npmbabel-cli^6.8.0indirect
npmbabel-core^6.8.0indirect
npmbabel-loader^6.2.4indirect
npmbabel-plugin-transform-export-extensions^6.8.0indirect
npmbabel-preset-es2015^6.3.13indirect
npmbiojs-io-newick^1.5.0indirect
npmchai^1.9.1indirect
npmcss-loader^0.23.1indirect
npmd3-scale^0.7.0indirect
npmgulp^3.8.7indirect
npmgulp-chmod^1.1.0indirect
npmgulp-concat^2.3.4indirect
npmgulp-gzip0.0.8indirect
npmgulp-minify-css^0.3.7indirect
npmgulp-mocha^0.5.2indirect
npmgulp-rename^1.2.0indirect
npmgulp-uglify^0.3.1indirect
npmmkdirp-then^1.1.1indirect
npmmocha^1.21.4indirect
npmmsa-tnt^0.1.20indirect
npmprunner^1.0.0indirect
npmsinon^1.12.1indirect
npmsniper^0.2.16indirect
npmstrip-loader^0.1.2indirect
npmstyle-loader^0.13.0indirect
npmthrough2^0.6.3indirect
npmtnt.tree0.1.4indirect
npmuglify-js~2.6.2indirect
npmwebpack^1.13.0indirect
Dependency advisories 5

Installing npm:msa@1.0.3 pulls in 79 packages, direct and transitive: 5 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
form-data2.3.3indirecthigh24.0.6
uuid3.4.0indirecthigh113.0.1
qs6.5.5indirectmoderate26.16.0
request2.88.2indirectmoderate13.0.0
tough-cookie2.5.0indirectmoderate14.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.

The message is kept through sign-in.

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.