Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 16:41 UTC

nuxt-modules / fontaine

🔤 Font metric overrides to reduce CLS

TypeScript · VueMIT★ 440 stars⑂ 14 forkssince Sep 2022View on GitHub ↗

nuxt-modules/fontaine holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (78/100) and lowest on AI Readiness (52/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

83
overall / 100
Excellent

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.

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

Ownership

Nuxt ModulesOrganization
460 followers43 public repossince Aug 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@nuxtjs/fontaine0.5.063,25911574 days agonuxtmodulenuxt-modulefontsclsweb-vitalsperformance

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
26.3/36Commit cadence38/52 weeks with commits
18/18Commit volume145 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year145
human_commit_share0.06
days_since_last_push3
active_weeks_last_year38
How it's scored
27/27Ships releases15 releases published
7.2/36Release recencylatest release 574 days ago
19.8/27Release cadencea release every ~90.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count15
latest_release_tagv0.5.0
releases_from_tagsno
days_since_latest_release574
mean_days_between_releases90.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?

66Good · 17% of overall
How it's scored
42.9/60Stars440 stars
9.3/25Forks14 forks
0/15Watchers2 watchers
Inputs used
forks14
stars440
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
64/80Monthly downloads63,259 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@nuxtjs/fontaine
dependents
ecosystemsnpm
total_downloads
monthly_downloads63,259
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.7/22.5Commit distributiontop contributor authored 92% of commits
12.2/13.5Contributor breadth9 contributors
10/10OpenSSF Scorecard: Contributorsproject has 15 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.923
How it's scored
29.6/42Issue resolution70% of issues closed
29.4/30PR acceptance691/704 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs691
open_issues8
closed_issues19
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.704
closed_unmerged_prs13
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 backingorganization-owned
0/20Verified domain
19.2/25Owner reach460 followers of nuxt-modules
20.1/25Track record43 public repos, account ~4 yr old
Inputs used
followers460
owner_typeOrganization
is_verifiedno
owner_loginnuxt-modules
public_repos43
account_age_days1,488
How it's scored
25/25Published & resolvable1 package(s) on npm
14/35Publish recencylatest publish 574 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@nuxtjs/fontaine
ecosystemsnpm
any_deprecatedno
min_days_since_publish574

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests29 out of 29 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicsperformance, web-vitals, cls, nuxt, nuxt-module, hacktoberfest
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?

76Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/2 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 15 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7
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 advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages72
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:@nuxtjs/fontaine@0.5.0 runtime dependency closure — what installing the published package pulls in — 72 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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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
11/11Lint / format configeslint.config.js
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance94 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.94
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/9 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes5,739
source_files_sampled9
oversized_source_files0

Key facts

440GitHub stars
9contributors
145commits, last 12 months
3days since last push
15releases
1bus factor
8open 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 ★ / 14 ⇿
0Stars
14Forks
12Releases

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.

03581013151422022-092023-112025-01
Major 0Minor 3Patch 9

Each point covers 3 days.

OpenSSF Scorecard 7.0 / 10
7.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-18 16:41 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 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/2 approved changesets -- score normalized to 0
10Contributorsproject has 15 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 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npm@nuxt/kit^4.0.0package.json
npmfontaine^0.8.0package.json
npmmagic-string^0.30.17package.json
npmpathe^2.0.3package.json
npmufo^1.5.4package.json
All dependencies 21

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

RegistryPackageVersionRelation
npm@nuxtjs/fontainelatestindirect
npm@pnpm/exe11.25.0indirect
npm@pnpm/linux-arm6411.25.0indirect
npm@pnpm/linux-x6411.25.0indirect
npm@pnpm/linuxstatic-arm6411.25.0indirect
npm@pnpm/linuxstatic-x6411.25.0indirect
npm@pnpm/macos-arm6411.25.0indirect
npm@pnpm/win-arm6411.25.0indirect
npm@pnpm/win-x6411.25.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
npmdetect-libc2.1.2indirect
npmnuxt4.5.2indirect
npmpnpm11.25.0indirect
Dependency advisories 0

Installing npm:@nuxtjs/fontaine@0.5.0 pulls in 72 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 statisticsnpm.