Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 16:24 UTC

htunnicliff / jmap-jam

Jam is a tiny (~2kb gzipped), strongly-typed JMAP client with zero runtime dependencies. It has friendly, fluent APIs that make working with JMAP a breeze.

TypeScriptNo license detected★ 91 stars⑂ 4 forkssince Oct 2023View on GitHub ↗

htunnicliff/jmap-jam holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (91/100) and lowest on AI Readiness (35/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Hunter TunnicliffPersonal account
48 followers86 public repossince May 2014@transcend-io

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
npmjmap-jam0.13.710,232340 days ago
npmjmap-rfc-types0.4.110,66090 days ago

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
25.6/36Commit cadence — 37/52 weeks with commits
18/18Commit volume — 334 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year334
human_commit_share0.15
days_since_last_push0
active_weeks_last_year37
How it's scored
27/27Ships releases — 23 releases published
36/36Release recency — latest release 79 days ago
19.8/27Release cadence — a release every ~63.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv0.13.2
releases_from_tagsno
days_since_latest_release79
mean_days_between_releases63.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
31.7/60Stars — 91 stars
4/25Forks — 4 forks
1.7/15Watchers — 3 watchers
Inputs used
forks4
stars91
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
57.6/80Monthly downloads — 20,892 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesjmap-jam, jmap-rfc-types
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads20,892
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 factor — 1 contributor(s) cover half of all commits
0.4/22.5Commit distribution — top contributor authored 98% of commits
5.4/13.5Contributor breadth — 4 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.982
How it's scored
28.9/42Issue resolution — 69% of issues closed
27/30PR acceptance — 326/362 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 1/4 approved changesets -- score normalized to 2
Inputs used
merged_prs326
open_issues5
closed_issues11
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.688
closed_unmerged_prs36
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.2/25Owner reach — 48 followers of htunnicliff
25/25Track record — 86 public repos, account ~12 yr old
Inputs used
followers48
owner_typeUser
is_verified—
owner_loginhtunnicliff
public_repos86
account_age_days4,500
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on npm
35/35Publish recency — latest publish 0 days ago
20/20Version history — 34 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjmap-jam, jmap-rfc-types
ecosystemsnpm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 23 out of 27 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsno
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
10/10Topics — 2 topics
0/10Wiki
Inputs used
topicsjmap, jmap-client
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?

63Moderate · 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
2/2.5CI-Tests — 23 out of 27 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 1/4 approved changesets -- score normalized to 2
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
3.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.4
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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
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:jmap-jam@0.13.7 runtime dependency closure — what installing the published package pulls in — 3 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/jmap-jam/tsconfig.json, packages/jmap-rfc-types/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 80 of the last 100 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/jmap-jam/tsconfig.json, packages/jmap-rfc-types/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.8
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/26 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes57,250
source_files_sampled26
oversized_source_files0

Key facts

91GitHub stars
4contributors
334commits, last 12 months
0days since last push
23releases
1bus factor
5open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-15: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 91 stars today.

More detail

Star and fork history 89 ★ / 4 ⇿
89Stars
4Forks
17Releases

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.

Star history is shown as collected on 2026-07-15. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02040608010089432023-102025-032026-07
Major 0Minor 9Patch 8

Each point covers 3 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-12 16:24 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
8CI-Tests23 out of 27 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 1/4 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmjmap-rfc-typesworkspace:*packages/jmap-jam/package.json
npmtype-festcatalog:packages/jmap-jam/package.json
npmtype-festcatalog:packages/jmap-rfc-types/package.json
All dependencies 20

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

RegistryPackageVersionRelation
npmtype-festcatalog:direct
npm@arethetypeswrong/corecatalog:indirect
npm@pnpm/exe.android-arm6412.4.0indirect
npm@pnpm/exe.android-x6412.4.0indirect
npm@pnpm/exe.darwin-arm6412.4.0indirect
npm@pnpm/exe.darwin-x6412.4.0indirect
npm@pnpm/exe.freebsd-x6412.4.0indirect
npm@pnpm/exe.linux-arm6412.4.0indirect
npm@pnpm/exe.linux-arm64-musl12.4.0indirect
npm@pnpm/exe.linux-ppc6412.4.0indirect
npm@pnpm/exe.linux-riscv6412.4.0indirect
npm@pnpm/exe.linux-s390x12.4.0indirect
npm@pnpm/exe.linux-x6412.4.0indirect
npm@pnpm/exe.linux-x64-musl12.4.0indirect
npm@pnpm/exe.win32-arm6412.4.0indirect
npm@pnpm/exe.win32-x6412.4.0indirect
npmpnpm12.4.0indirect
npmtsdowncatalog:indirect
npmtypescriptcatalog:indirect
npmvitestcatalog:indirect
Dependency advisories 0

Installing npm:jmap-jam@0.13.7 pulls in 3 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 statistics — npm.