Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 16:50 UTC

voxpelli / read-workspaces

Like "read-pkg" but for an entire workspace

JavaScriptMIT★ 2 stars⑂ 0 forkssince Mar 2024View on GitHub ↗

voxpelli/read-workspaces holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (66/100) and lowest on Community & Adoption (45/100). It was last updated 50 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Pelle WessmanPersonal account
611 followers226 public repossince Nov 2008@040-Internet-AB

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 publish
npmread-workspaces2.0.060,6517106 days ago

Metrics by category

Vitality

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

46Weak · 21% of overall
How it's scored
18/36Push recency — last push 50 days ago
0.7/36Commit cadence — 1/52 weeks with commits
8.1/18Commit volume — 7 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_year7
human_commit_share0.784
days_since_last_push50
active_weeks_last_year1
How it's scored
27/27Ships releases — 7 releases published
27/36Release recency — latest release 106 days ago
12.6/27Release cadence — a release every ~143.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv2.0.0
releases_from_tagsno
days_since_latest_release106
mean_days_between_releases143.5
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
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
63.8/80Monthly downloads — 60,651 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesread-workspaces
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads60,651
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
28/42Issue resolution — 67% of issues closed
12.4/30PR acceptance — 12/29 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs12
open_issues1
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.667
closed_unmerged_prs17
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
20/25Owner reach — 611 followers of voxpelli
25/25Track record — 226 public repos, account ~18 yr old
Inputs used
followers611
owner_typeUser
is_verified—
owner_loginvoxpelli
public_repos226
account_age_days6,578
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 106 days ago
20/20Version history — 7 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesread-workspaces
ecosystemsnpm
any_deprecatedno
min_days_since_publish106

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 4 out of 11 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
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?

64Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.8/2.5CI-Tests — 4 out of 11 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/22 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 8 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — 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
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
12.7/25Indirect dependencies free of known advisories — 2 affected: glob 13.0.7 (moderate 5.3), minimatch 10.2.6 (moderate 5.3)
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages54
unassessed_packages0
affected_by_severitymoderate 2
direct_affected_packages0
Matched the npm:read-workspaces@2.0.0 runtime dependency closure — what installing the published package pulls in — 54 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.

66Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
31.3/40Legible commit history — 17 of 29 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.586
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,475
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 37
8/8Automated maintenance — 5 of the last 37 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.135
How it's scored
27/45Type-checkable code — JavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,788
source_files_sampled5
oversized_source_files0

Key facts

2GitHub stars
1contributors
7commits, last 12 months
50days since last push
7releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.8 / 10
5.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-11-18 16:50 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
3CI-Tests4 out of 11 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/22 approved changesets -- score normalized to 0
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
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
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npm@npmcli/map-workspaces^6.0.0package.json
npm@pnpm/workspace.read-manifest^1000.3.0package.json
npm@voxpelli/typed-utils^5.0.0package.json
npmread-pkg^10.1.0package.json
All dependencies 19

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

RegistryPackageVersionRelation
npm@npmcli/map-workspaces^6.0.0direct
npm@pnpm/workspace.read-manifest^1000.3.0direct
npm@voxpelli/typed-utils^5.0.0direct
npmread-pkg^10.1.0direct
npm@types/node^22.20.1indirect
npm@types/npmcli__map-workspaces^3.0.4indirect
npm@voxpelli/eslint-config^25.1.0indirect
npm@voxpelli/tsconfig^16.2.1indirect
npmc8^12.0.0indirect
npmeslint^9.39.5indirect
npmhusky^9.1.7indirect
npminstalled-check^10.0.1indirect
npmknip^6.31.0indirect
npmnpm-run-all2^9.0.3indirect
npmpony-cause^2.1.11indirect
npmtstyche^7.2.2indirect
npmtype-coverage^2.30.1indirect
npmtypescript~6.0.3indirect
npmvalidate-conventional-commit^1.0.4indirect
Dependency advisories 2

Installing npm:read-workspaces@2.0.0 pulls in 54 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
glob13.0.7indirectmoderate114.0.2
minimatch10.2.6indirectmoderate111.0.1

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.