Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 18:21 UTC

i-VRESSE / pdbtbx-ts

JS wrapper around pdbtbx rust crate

Rust · JavaScriptApache-2.0★ 1 star⑂ 1 forksince Apr 2022View on GitHub ↗

i-VRESSE/pdbtbx-ts holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (49/100) and lowest on Vitality (25/100). It was last updated 854 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

2 followers20 public repossince Nov 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@i-vresse/pdbtbx-ts0.1.756881588 days agopdbmmcifparse

Metrics by category

Vitality

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

25At Risk · 21% of overall
How it's scored
0/36Push recency — last push 854 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push854
active_weeks_last_year0
How it's scored
27/27Ships releases — 3 releases published
0/36Release recency — latest release 1,588 days ago
27/27Release cadence — a release every ~19.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv0.1.7
releases_from_tagsno
days_since_latest_release1,588
mean_days_between_releases19.4
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?

42Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 1 forks
3.3/15Watchers — 5 watchers
Inputs used
forks1
stars1
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
36.7/80Monthly downloads — 568 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@i-vresse/pdbtbx-ts
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads568
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?

42Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.3/22.5Commit distribution — top contributor authored 94% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.943
How it's scored
0/42Issue resolution — 0% of issues closed
30/30PR acceptance — 3/3 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs3
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs0
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 backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of i-VRESSE
19.6/25Track record — 20 public repos, account ~4 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_logini-VRESSE
public_repos20
account_age_days1,813
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,588 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@i-vresse/pdbtbx-ts
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,588

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 2 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
0/7.5Code-Review — Found 0/19 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 18 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
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 — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 22 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories22
affected_packages10
assessed_packages110
unassessed_packages6
affected_by_severitycritical 1, high 5, moderate 3, low 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 110 resolved dependencies against OSV. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3/40Legible commit history — 2 of 35 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.057
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 35
0/8Automated maintenance — no automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/4 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes3,344
source_files_sampled4
oversized_source_files0

Key facts

1GitHub stars
2contributors
0commits, last 12 months
854days since last push
3releases
1bus factor
1open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'pdbtbx-ts' from its registry

More detail

OpenSSF Scorecard 2.5 / 10
2.5aggregate

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-22 18:21 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 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/19 approved changesets -- score normalized to 0
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities22 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
crates.iopdbtbx0.9.1Cargo.toml
crates.iowasm-bindgen0.2.81Cargo.toml
crates.ioserde1.0Cargo.toml
crates.ioserde-wasm-bindgen0.4.3Cargo.toml
crates.ioconsole_error_panic_hook0.1.7Cargo.toml
crates.iowee_alloc0.4.5Cargo.toml
All dependencies 116

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

RegistryPackageVersionRelation
crates.ioconsole_error_panic_hook—direct
crates.iopdbtbx—direct
crates.ioserde—direct
crates.ioserde-wasm-bindgen—direct
crates.iowasm-bindgen—direct
crates.iowee_alloc—direct
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@types/node18.0.0indirect
npmany-promise1.3.0indirect
npmanymatch3.1.2indirect
npmarray-union2.1.0indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.2.0indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.2indirect
npmbundle-require3.0.4indirect
npmcac6.7.12indirect
npmchokidar3.5.3indirect
npmcommander4.1.1indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.3indirect
npmdebug4.3.4indirect
npmdir-glob3.0.1indirect
npmesbuild0.14.43indirect
npmesbuild-android-640.14.43indirect
npmesbuild-android-arm640.14.43indirect
npmesbuild-darwin-640.14.43indirect
npmesbuild-darwin-arm640.14.43indirect
npmesbuild-freebsd-640.14.43indirect
npmesbuild-freebsd-arm640.14.43indirect
npmesbuild-linux-320.14.43indirect
npmesbuild-linux-640.14.43indirect
npmesbuild-linux-arm0.14.43indirect
npmesbuild-linux-arm640.14.43indirect
npmesbuild-linux-mips64le0.14.43indirect
npmesbuild-linux-ppc64le0.14.43indirect
npmesbuild-linux-riscv640.14.43indirect
npmesbuild-linux-s390x0.14.43indirect
npmesbuild-netbsd-640.14.43indirect
npmesbuild-openbsd-640.14.43indirect
npmesbuild-sunos-640.14.43indirect
npmesbuild-windows-320.14.43indirect
npmesbuild-windows-640.14.43indirect
npmesbuild-windows-arm640.14.43indirect
npmexeca5.1.1indirect
npmfast-glob3.2.11indirect
npmfastq1.13.0indirect
npmfill-range7.0.1indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.2indirect
npmget-stream6.0.1indirect
npmglob7.1.6indirect
npmglob-parent5.1.2indirect
npmglobby11.1.0indirect
npmhuman-signals2.1.0indirect
npmignore5.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-stream2.0.1indirect
npmisexe2.0.0indirect
npmjoycon3.1.1indirect
npmlilconfig2.0.5indirect
npmlines-and-columns1.2.4indirect
npmload-tsconfig0.2.3indirect
npmlodash.sortby4.7.0indirect
npmmerge-stream2.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.5indirect
npmmimic-fn2.1.0indirect
npmminimatch3.1.2indirect
npmms2.1.2indirect
npmmz2.7.0indirect
npmnormalize-path3.0.0indirect
npmnpm-run-path4.0.1indirect
npmobject-assign4.1.1indirect
npmonce1.4.0indirect
npmonetime5.1.2indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-type4.0.0indirect
npmpicomatch2.3.1indirect
npmpirates4.0.5indirect
npmpostcss-load-config3.1.4indirect
npmpunycode2.1.1indirect
npmqueue-microtask1.2.3indirect
npmreaddirp3.6.0indirect
npmresolve-from5.0.0indirect
npmreusify1.0.4indirect
npmrollup2.75.6indirect
npmrun-parallel1.2.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit3.0.7indirect
npmslash3.0.0indirect
npmsource-map0.8.0-beta.0indirect
npmstrip-final-newline2.0.0indirect
npmsucrase3.21.0indirect
npmthenify3.3.1indirect
npmthenify-all1.6.0indirect
npmto-regex-range5.0.1indirect
npmtr461.0.1indirect
npmtree-kill1.2.2indirect
npmts-interface-checker0.1.13indirect
npmtsup6.1.2indirect
npmtypescript4.7.3indirect
npmwebidl-conversions4.0.2indirect
npmwhatwg-url7.1.0indirect
npmwhich2.0.2indirect
npmwrappy1.0.2indirect
npmyaml1.10.2indirect
Dependency advisories 10

This repository publishes no package the index resolves, so its own dependency graph was assessed — 110 packages, which also include development and test pins that never ship: 10 carry known advisories, of which 0 are direct. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
rollup2.75.6indirectcritical24.59.0
brace-expansion1.1.11indirecthigh85.0.12
braces3.0.2indirecthigh23.0.3
cross-spawn7.0.3indirecthigh17.0.5
minimatch3.1.2indirecthigh310.2.3
picomatch2.3.1indirecthigh24.0.4
esbuild0.14.43indirectmoderate10.25.0
micromatch4.0.5indirectmoderate14.0.8
yaml1.10.2indirectmoderate12.8.3
tsup6.1.2indirectlow1—

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.