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

Uauy-Lab / biojs-vis-expression-bar

JavaScriptMIT★ 2 stars⑂ 5 forkssince Jun 2015View on GitHub ↗

Uauy-Lab/biojs-vis-expression-bar holds a health index of 17 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (56/100) and lowest on Vitality (13/100). It was last updated 1738 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Uauy-LabOrganization
13 followers21 public repossince May 2018

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmbio-vis-expression-bar0.9.1170561738 days agorna-seqgene-expressionbarchartbiojsheatmapternary-plot

Metrics by category

Vitality

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

13Critical · 21% of overall
How it's scored
0/36Push recencylast push 1,738 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.91
days_since_last_push1,738
active_weeks_last_year0
How it's scored
16.2/27Ships releases11 version tags (no GitHub releases)
0/36Release recencylatest release 1,743 days ago
12.6/27Release cadencea release every ~162.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tag0.9.0
releases_from_tagsyes
days_since_latest_release1,743
mean_days_between_releases162.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?

29At Risk · 17% of overall
How it's scored
0/60Stars2 stars
5/25Forks5 forks
0/15Watchers1 watchers
Inputs used
forks5
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicestravis-ci.org
has_pull_request_templateno
How it's scored
29.8/80Monthly downloads170 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesbio-vis-expression-bar
dependents
ecosystemsnpm
total_downloads
monthly_downloads170
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.6/22.5Commit distributiontop contributor authored 53% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.528
How it's scored
35/42Issue resolution83% of issues closed
24.4/30PR acceptance22/27 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs22
open_issues8
closed_issues40
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.833
closed_unmerged_prs5
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
30/30Ownership backingorganization-owned
0/20Verified domain
8.2/25Owner reach13 followers of Uauy-Lab
21.8/25Track record21 public repos, account ~8 yr old
Inputs used
followers13
owner_typeOrganization
is_verifiedno
owner_loginUauy-Lab
public_repos21
account_age_days3,032
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 1,738 days ago
20/20Version history56 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbio-vis-expression-bar
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,738

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 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-Tests0 out of 10 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
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

51Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/11 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.9
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/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages270
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:bio-vis-expression-bar@0.9.1 runtime dependency closure — what installing the published package pulls in — 270 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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.2/40Legible commit history14 of 91 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.154
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 practiceno agent-authored commits among the last 100
8/8Automated maintenance9 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
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.09
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
42.8/55Manageable file sizes8/36 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes1,545,134
source_files_sampled36
oversized_source_files8

Key facts

2GitHub stars
3contributors
0commits, last 12 months
1,738days since last push
11releases
1bus factor
8open 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 ★ / 5 ⇿
0Stars
5Forks
5Releases

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.

12345512015-062017-012018-08
Major 0Minor 2Patch 3

Each point covers 3 days.

OpenSSF Scorecard 3.9 / 10
3.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:35 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/11 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
npm@babel/core^7.16.0package.json
npm@babel/preset-env^7.16.4package.json
npmbabel-loader^8.2.3package.json
npmcolorbrewer1.1package.json
npmcss-loader^6.5.1package.json
npmd37package.json
npmfile-loader^6.2.0package.json
npmjquery^3.6.0package.json
npmjquery-ui^1.13.0package.json
npmsass-loader^12.3.0package.json
npmscience~1.9.3package.json
npmstring.prototype.startswith0.2.0package.json
npmstyle-loader^3.3.1package.json
npmwebpack^5.64.3package.json
All dependencies 36

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

RegistryPackageVersionRelation
npm@babel/core^7.16.0direct
npm@babel/preset-env^7.16.4direct
npmbabel-loader^8.2.3direct
npmcolorbrewer1.1direct
npmcss-loader^6.5.1direct
npmd37direct
npmfile-loader^6.2.0direct
npmjquery>=1.8.0 <4.0.0direct
npmjquery^3.6.0direct
npmjquery-ui^1.13.0direct
npmsass-loader^12.3.0direct
npmscience~1.9.3direct
npmstring.prototype.startswith0.2.0direct
npmstyle-loader^3.3.1direct
npmwebpack^5.64.3direct
npmcommitplease3.2.0indirect
npmeslint-config-jquery3.0.0indirect
npmglob7.1.7indirect
npmgrunt1.4.1indirect
npmgrunt-bowercopy1.2.5indirect
npmgrunt-cli1.4.3indirect
npmgrunt-compare-size0.4.2indirect
npmgrunt-contrib-concat1.0.1indirect
npmgrunt-contrib-csslint2.0.0indirect
npmgrunt-contrib-qunit5.0.1indirect
npmgrunt-contrib-requirejs1.0.0indirect
npmgrunt-contrib-uglify5.0.1indirect
npmgrunt-eslint23.0.0indirect
npmgrunt-git-authors3.2.0indirect
npmgrunt-html14.5.0indirect
npmload-grunt-tasks5.1.0indirect
npmrimraf3.0.2indirect
npmsniper^0.2.16indirect
npmtestswarm1.1.2indirect
npmwebpack-cli^4.9.1indirect
npmwebpack-dev-server^4.6.0indirect
Dependency advisories 0

Installing npm:bio-vis-expression-bar@0.9.1 pulls in 270 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.

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