Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 18:40 UTC

JeromeFitz / packages

Monorepo for stuff that I use frequently: Commit Generator, Gitmoji, Oxc, Notion, Semantic Release, etc.

TypeScriptMIT★ 77 stars⑂ 7 forkssince Apr 2021View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

JeromeFitz/packages holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (96/100) and lowest on AI Readiness (42/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Jerome FitzgeraldPersonal account
43 followers106 public repossince Dec 2012@IBM

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 publishTags
npm@jeromefitz/utils4.2.02215072 days agoutilitiesutils
npm@jeromefitz/tsconfig3.2.02022072 days ago—
npm@jeromefitz/notion7.0.669911320 days agonextnext.jsnotion
npmccommit4.2.23185055 days agocommitconventional-changelogconventional-commitsenquirerformatgitflowgithubflowgitmojisemver
npm@jeromefitz/scripts9.2.012818072 days ago—
npm@jeromefitz/semantic12.2.343323234 days ago—
npm@jeromefitz/conventional-gitmoji5.2.04027172 days ago—
npm@jeromefitz/release-notes-generator4.2.23728141 days ago—

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 301 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year301
human_commit_share0.16
days_since_last_push2
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 20 days ago
27/27Release cadence — a release every ~4.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag@jeromefitz/notion@7.0.6
releases_from_tagsno
days_since_latest_release20
mean_days_between_releases4.7
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
30.5/60Stars — 77 stars
6.5/25Forks — 7 forks
0/15Watchers — 0 watchers
Inputs used
forks7
stars77
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
45.9/80Monthly downloads — 2,775 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@jeromefitz/utils, @jeromefitz/tsconfig, @jeromefitz/notion, ccommit, @jeromefitz/scripts, @jeromefitz/semantic, @jeromefitz/conventional-gitmoji, @jeromefitz/release-notes-generator
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,775
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?

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.2/22.5Commit distribution — top contributor authored 90% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.9
How it's scored
40.7/42Issue resolution — 97% of issues closed
28.4/30PR acceptance — 2,466/2,605 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs2,466
open_issues1
closed_issues31
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.969
closed_unmerged_prs139
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
11.8/25Owner reach — 43 followers of JeromeFitz
25/25Track record — 106 public repos, account ~13 yr old
Inputs used
followers43
owner_typeUser
is_verified—
owner_loginJeromeFitz
public_repos106
account_age_days5,014
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on npm
35/35Publish recency — latest publish 20 days ago
20/20Version history — 232 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@jeromefitz/utils, @jeromefitz/tsconfig, @jeromefitz/notion, ccommit, @jeromefitz/scripts, @jeromefitz/semantic, @jeromefitz/conventional-gitmoji, @jeromefitz/release-notes-generator
ecosystemsnpm
any_deprecatedno
min_days_since_publish20

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://jeromefitzgerald.com
10/10Repository description
10/10Topics — 13 topics
0/10Wiki
Inputs used
topicsturborepo, semantic-release, gitmoji, notion, pnpm, tsconfig, turbo, syncpack, conventional-commit, emoji, oxfmt, oxlint, tsdown
has_wikino
homepagehttps://jeromefitzgerald.com
docs_sitehttps://jeromefitzgerald.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 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
7.5/7.5Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
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
advisories3
affected_packages1
assessed_packages53
unassessed_packages0
affected_by_severityhigh 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 53 resolved dependencies against OSV. 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.

42Weak · 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
22/22Automated tests
0/11Lint / format config
11/11Static type checking — config/oxlint-config/tsconfig.json, packages/ccommit/tsconfig.json, packages/conventional-gitmoji/tsconfig.json, packages/notion/tsconfig.json, packages/release-notes-generator/tsconfig.json, packages/scripts/tsconfig.json, packages/semantic/tsconfig.json, packages/utils/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 84 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configsconfig/oxlint-config/tsconfig.json, packages/ccommit/tsconfig.json, packages/conventional-gitmoji/tsconfig.json, packages/notion/tsconfig.json, packages/release-notes-generator/tsconfig.json, packages/scripts/tsconfig.json, packages/semantic/tsconfig.json, packages/utils/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.84
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/190 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes31,701
source_files_sampled190
oversized_source_files0

Key facts

77GitHub stars
2contributors
301commits, last 12 months
2days since last push
100releases
1bus factor
1open 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 ★ / 7 ⇿
0Stars
7Forks

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.

1234567712022-012023-072025-01

Each point covers 3 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-13 18:40 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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/30 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 54
RegistryPackageVersion constraintManifest
npm@arethetypeswrong/core0.18.2package.json
npm@jeromefitz/conventional-gitmojiworkspace:*package.json
npm@jeromefitz/oxlint-configworkspace:*package.json
npm@jeromefitz/release-notes-generatorworkspace:*package.json
npm@jeromefitz/semanticworkspace:*package.json
npm@jeromefitz/tsconfigworkspace:*package.json
npm@types/node24.12.0package.json
npm@vitest/coverage-v84.1.9package.json
npmccommitworkspace:*package.json
npmdotenv17.4.2package.json
npmis-in-ci2.0.0package.json
npmlint-staged17.0.5package.json
npmlodash-es4.18.0package.json
npmoxfmt0.56.0package.json
npmpublint0.3.21package.json
npmsemantic-release25.0.3package.json
npmsyncpack15.3.1package.json
npmtsdown0.22.0package.json
npmturbo2.9.14package.json
npmtypescript5.9.3package.json
npmvitest4.1.9package.json
npm@typescript-eslint/utils8.70.0config/oxlint-config/package.json
npmeslint10.10.0config/oxlint-config/package.json
npmeslint-plugin-playwright2.11.0config/oxlint-config/package.json
npmeslint-plugin-testing-library7.16.2config/oxlint-config/package.json
npmglobals17.12.0config/oxlint-config/package.json
npmoxlint1.78.0config/oxlint-config/package.json
npmoxlint-tsgolint0.25.0config/oxlint-config/package.json
npmansi-colors4.1.3packages/ccommit/package.json
npmenquirer2.4.1packages/ccommit/package.json
npmexeca9.6.1packages/ccommit/package.json
npmfuse.js7.5.0packages/ccommit/package.json
npmmeow14.1.0packages/ccommit/package.json
npmfast-json-stable-stringify2.1.0packages/conventional-gitmoji/package.json
npmgrapheme-splitter1.0.4packages/conventional-gitmoji/package.json
npmtitle4.0.1packages/conventional-gitmoji/package.json
npm@notionhq/client5.26.0packages/notion/package.json
npmdate-fns4.4.0packages/notion/package.json
npmgithub-slugger2.0.0packages/notion/package.json
npm@octokit/rest22.0.1packages/release-notes-generator/package.json
npmconventional-commits-filter6.0.1packages/release-notes-generator/package.json
npmconventional-commits-parser7.1.2packages/release-notes-generator/package.json
npmdate-fns4.4.0packages/release-notes-generator/package.json
npmread-package-up12.0.0packages/release-notes-generator/package.json
npmsemver7.8.5packages/release-notes-generator/package.json
npm@octokit/rest22.0.1packages/scripts/package.json
npmcolorize-template1.0.0packages/scripts/package.json
npmis-in-ci2.0.0packages/scripts/package.json
npmpicocolors1.1.1packages/scripts/package.json
npm@semantic-release/commit-analyzer13.0.1packages/semantic/package.json
npm@semantic-release/git10.0.1packages/semantic/package.json
npmsemantic-release25.0.9packages/semantic/package.json
npmsemantic-release-commit-filter1.0.2packages/semantic/package.json
npmtitle4.0.1packages/semantic/package.json
All dependencies 53

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

RegistryPackageVersionRelation
npm@notionhq/client5.26.0direct
npm@octokit/rest22.0.1direct
npm@semantic-release/commit-analyzer13.0.1direct
npm@semantic-release/git10.0.1direct
npm@types/node24.13.4direct
npm@typescript-eslint/utils8.70.0direct
npmansi-colors4.1.3direct
npmcolorize-template1.0.0direct
npmconventional-commits-filter6.0.1direct
npmconventional-commits-parser7.1.2direct
npmdate-fns4.4.0direct
npmenquirer2.4.1direct
npmeslint10.10.0direct
npmeslint-plugin-playwright2.11.0direct
npmeslint-plugin-testing-library7.16.2direct
npmexeca9.6.1direct
npmfast-json-stable-stringify2.1.0direct
npmfuse.js7.5.0direct
npmgithub-slugger2.0.0direct
npmglobals17.12.0direct
npmgrapheme-splitter1.0.4direct
npmis-in-ci2.0.0direct
npmlodash-es4.18.0direct
npmmeow14.1.0direct
npmoxlint1.78.0direct
npmoxlint-tsgolint0.25.0direct
npmpicocolors1.1.1direct
npmread-package-up12.0.0direct
npmsemantic-release25.0.9direct
npmsemantic-release-commit-filter1.0.2direct
npmsemver7.8.5direct
npmtitle4.0.1direct
npm@pnpm/exe11.9.0indirect
npm@pnpm/linux-arm6411.9.0indirect
npm@pnpm/linux-x6411.9.0indirect
npm@pnpm/linuxstatic-arm6411.9.0indirect
npm@pnpm/linuxstatic-x6411.9.0indirect
npm@pnpm/macos-arm6411.9.0indirect
npm@pnpm/win-arm6411.9.0indirect
npm@pnpm/win-x6411.9.0indirect
npm@reflink/reflink0.1.19indirect
npm@reflink/reflink-darwin-arm640.1.19indirect
npm@reflink/reflink-darwin-x640.1.19indirect
npm@reflink/reflink-linux-arm64-gnu0.1.19indirect
npm@reflink/reflink-linux-arm64-musl0.1.19indirect
npm@reflink/reflink-linux-x64-gnu0.1.19indirect
npm@reflink/reflink-linux-x64-musl0.1.19indirect
npm@reflink/reflink-win32-arm64-msvc0.1.19indirect
npm@reflink/reflink-win32-x64-msvc0.1.19indirect
npm@types/lodash-es4.17.12indirect
npmdetect-libc2.1.2indirect
npmgitmojis3.15.0indirect
npmpnpm11.9.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 53 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
pnpm11.9.0indirecthigh311.11.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.