Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-25 22:33 UTC

metonym / svelte-highlight

Syntax Highlighting for Svelte using highlight.js

TypeScript · JavaScript · SvelteMIT★ 335 stars⑂ 14 forkssince Nov 2019View on GitHub ↗

metonym/svelte-highlight holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Community & Adoption (60/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Eric LiuPersonal account
294 followers161 public repossince Jan 2015@renderinc

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
npmsvelte-highlight7.16.0188,536896 days agosveltesvelte-componentshighlight.jssyntax-highlight

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
28.4/36Commit cadence41/52 weeks with commits
18/18Commit volume447 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year447
human_commit_share1
days_since_last_push2
active_weeks_last_year41

Release discipline

100Exceptional
How it's scored
27/27Ships releases69 releases published
36/36Release recencylatest release 6 days ago
27/27Release cadencea release every ~30.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count69
latest_release_tagv7.16.0
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases30.1
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?

60Moderate · 17% of overall
How it's scored
40.9/60Stars335 stars
9.3/25Forks14 forks
0/15Watchers2 watchers
Inputs used
forks14
stars335
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
70.3/80Monthly downloads188,536 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessvelte-highlight
dependents
ecosystemsnpm
total_downloads
monthly_downloads188,536
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
4.1/13.5Contributor breadth3 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.997
How it's scored
41.5/42Issue resolution99% of issues closed
26/30PR acceptance334/385 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs334
open_issues1
closed_issues81
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.988
closed_unmerged_prs51
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.8/25Owner reach294 followers of metonym
25/25Track record161 public repos, account ~11 yr old
Inputs used
followers294
owner_typeUser
is_verified
owner_loginmetonym
public_repos161
account_age_days4,197
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 6 days ago
20/20Version history89 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessvelte-highlight
ecosystemsnpm
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://svhe.onrender.com
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicssvelte, highlight-js, highlight, code, syntax, syntax-highlighting, svelte-component, typescript
has_wikino
homepagehttps://svhe.onrender.com
docs_sitehttps://svhe.onrender.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 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-Tests3 out of 3 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/7 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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 4 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities49 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): 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_packages2
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:svelte-highlight@7.16.0 runtime dependency closure — what installing the published package pulls in — 2 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.

64Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history96 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.96
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingexamples/rollup/tsconfig.json, examples/routify/tsconfig.json, examples/sveltekit/tsconfig.json, examples/vite/tsconfig.json, examples/vite@svelte-4/tsconfig.json, examples/webpack/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/rollup/tsconfig.json, examples/routify/tsconfig.json, examples/sveltekit/tsconfig.json, examples/vite/tsconfig.json, examples/vite@svelte-4/tsconfig.json, examples/webpack/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.8/55Manageable file sizes1/321 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes60,316
source_files_sampled321
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

335GitHub stars
3contributors
447commits, last 12 months
2days since last push
69releases
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 ★ / 14 ⇿
0Stars
14Forks
59Releases

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.

03581013151412020-042023-012025-10
Major 7Minor 18Patch 32

Each point covers 5 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-07-25 22:33 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests3 out of 3 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/7 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities49 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmmagic-string^0.30.17package.json
All dependencies 50

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

RegistryPackageVersionRelation
npmmagic-string^0.30.17direct
npm@astrojs/svelte^8.1.2indirect
npm@biomejs/biome2.5.5indirect
npm@playwright/experimental-ct-svelte1.58.2indirect
npm@playwright/test1.61.1indirect
npm@rollup/plugin-commonjslatestindirect
npm@rollup/plugin-node-resolvelatestindirect
npm@roxi/routify^3.6.4indirect
npm@sveltejs/adapter-nodelatestindirect
npm@sveltejs/kitlatestindirect
npm@sveltejs/vite-plugin-svelte^3.1.2indirect
npm@sveltejs/vite-plugin-svelte^5.1.1indirect
npm@sveltejs/vite-plugin-svelte^7.1.2indirect
npm@sveltejs/vite-plugin-sveltelatestindirect
npm@tsconfig/sveltelatestindirect
npm@types/bun^1.3.14indirect
npm@types/jest^30.0.0indirect
npm@types/node^25.9.5indirect
npm@typescript/native-preview^7.0.0-dev.20260707.2indirect
npmastro^6.4.8indirect
npmcarbon-components-svelte^0.110.1indirect
npmcarbon-preprocess-svelte^0.11.37indirect
npmcss-loaderlatestindirect
npmcssnano^7.1.9indirect
npmcssnano-preset-lite^4.0.6indirect
npmhighlight.js11.11.1indirect
npmhtml-webpack-pluginlatestindirect
npmmini-css-extract-pluginlatestindirect
npmpostcss^8.5.19indirect
npmpostcss-discard-duplicates^7.0.4indirect
npmpostcss-inline-css-vars^0.1.0indirect
npmpostcss-merge-rules^7.0.11indirect
npmrolluplatestindirect
npmrollup-plugin-sveltelatestindirect
npmrollup-plugin-terserlatestindirect
npmsvelte^4.2.20indirect
npmsvelte^5.56.3indirect
npmsvelte^5.56.6indirect
npmsveltelatestindirect
npmsvelte-highlight^7.16.0indirect
npmsvelte-loaderlatestindirect
npmsvelte-preprocesslatestindirect
npmtypescriptlatestindirect
npmvite^5.4.21indirect
npmvite^7.3.6indirect
npmvite^8.1.2indirect
npmvitelatestindirect
npmwebpacklatestindirect
npmwebpack-clilatestindirect
npmwebpack-dev-serverlatestindirect
Dependency advisories 0

Installing npm:svelte-highlight@7.16.0 pulls in 2 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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.