Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 12:11 UTC

ardriveapp / ardrive-core-js

ArDrive Core contains the essential back end application features to support the ArDrive CLI and Desktop apps, such as file management, Permaweb upload/download, wallet management and other common functions.

TypeScriptApache-2.0★ 59 stars⑂ 13 forkssince Sep 2020View on GitHub ↗

ardriveapp/ardrive-core-js holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Security (39/100). It was last updated 61 days ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

ArDrive AppOrganization
75 followers42 public repossince Aug 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmardrive-core-js4.3.01,02516775 days ago

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
18/36Push recency — last push 61 days ago
4.8/36Commit cadence — 7/52 weeks with commits
16.8/18Commit volume — 73 commits in the last year
10/10OpenSSF Scorecard: Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year73
human_commit_share1
days_since_last_push61
active_weeks_last_year7
How it's scored
27/27Ships releases — 42 releases published
16.2/36Release recency — latest release 236 days ago
19.8/27Release cadence — a release every ~69.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count42
latest_release_tagv4.0.0
releases_from_tagsno
days_since_latest_release236
mean_days_between_releases69.8
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?

47Weak · 17% of overall
How it's scored
28.6/60Stars — 59 stars
9/25Forks — 13 forks
4.7/15Watchers — 8 watchers
Inputs used
forks13
stars59
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
40.1/80Monthly downloads — 1,025 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesardrive-core-js
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,025
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.4/22.5Commit distribution — top contributor authored 54% of commits
13.5/13.5Contributor breadth — 13 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled13
top_contributor_share0.539
How it's scored
30.5/42Issue resolution — 73% of issues closed
26.5/30PR acceptance — 242/274 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs242
open_issues3
closed_issues8
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.727
closed_unmerged_prs32
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
13.5/25Owner reach — 75 followers of ardriveapp
23.9/25Track record — 42 public repos, account ~6 yr old
Inputs used
followers75
owner_typeOrganization
is_verifiedno
owner_loginardriveapp
public_repos42
account_age_days2,260

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 75 days ago
20/20Version history — 167 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesardrive-core-js
ecosystemsnpm
any_deprecatedno
min_days_since_publish75

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 11 out of 11 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

39Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/11 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 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
7.5/7.5Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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 — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 169 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
9.2/35Direct dependencies free of known advisories — 2 affected: axios 0.21.4 (high 8.6), uuid 9.0.1 (high 7.5)
4.1/25Indirect dependencies free of known advisories — 9 affected: bigint-buffer 1.1.5 (high 7.5), decode-uri-component 0.2.2 (high 7.5), elliptic 6.5.4 (high 7.5), +6 more
14.8/40No advisories left outstanding — 9 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,075 days ago
Inputs used
sourceosv
advisories43
affected_packages11
assessed_packages652
unassessed_packages0
affected_by_severityhigh 10, moderate 1
direct_affected_packages2
Matched the npm:ardrive-core-js@4.3.0 runtime dependency closure — what installing the published package pulls in — 652 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.95
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes6,707
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 43 of the last 100 commits agent-authored or agent-credited
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
lockfilespackage-lock.json, yarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.43
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53.5/55Manageable file sizes — 6/216 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,228,925
source_files_sampled216
oversized_source_files6
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 — examples
Inputs used
example_dirsexamples
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

59GitHub stars
13contributors
73commits, last 12 months
61days since last push
42releases
1bus factor
3open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 13 ⇿
0Stars
13Forks
37Releases

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.

03581013151312020-112023-032025-07
Major 2Minor 17Patch 18

Each point covers 5 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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:11 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
10CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/11 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities169 existing vulnerabilities detected
Direct dependencies 20
RegistryPackageVersion constraintManifest
npm@ardrive/ardrive-promise-cache^1.1.4package.json
npm@ardrive/turbo-sdk^1.0.1package.json
npm@dha-team/arbundles^1.0.3package.json
npm@noble/ciphers^2.0.1package.json
npm@noble/hashes^2.0.1package.json
npmarweave^1.15.7package.json
npmaxios^0.21.1package.json
npmaxios-retry^3.6.0package.json
npmbase64-js^1.5.1package.json
npmbignumber.js^9.1.2package.json
npmbn.js^5.2.1package.json
npmfutoin-hkdf^1.5.3package.json
npmhuman-crypto-keysgit+https://github.com/ardriveapp/js-human-crypto-keys.git#expose_libpackage.json
npmjwk-to-pem^2.0.5package.json
npmlodash^4.17.21package.json
npmmime-types^2.1.35package.json
npmregression^2.0.1package.json
npmsmartweave^0.4.49package.json
npmutf8^3.0.0package.json
npmuuid^9.0.1package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 11

Installing npm:ardrive-core-js@4.3.0 pulls in 652 packages, direct and transitive: 11 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
axios0.21.4directhigh231.18.0
uuid9.0.1directhigh113.0.1
bigint-buffer1.1.5indirecthigh1—
decode-uri-component0.2.2indirecthigh10.5.0
elliptic6.5.4indirecthigh76.6.1
elliptic6.6.1indirecthigh1—
secp256k15.0.0indirecthigh15.0.1
uuid8.3.2indirecthigh113.0.1
ws7.4.6indirecthigh28.21.0
ws8.18.0indirecthigh28.21.0
stream-json1.9.1indirectmoderate33.6.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.

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.