Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 15:09 UTC

spatie / commonmark-shiki-highlighter

Highlight code blocks with league/commonmark and Shiki

PHPMIT★ 92 stars⑂ 15 forkssince Jul 2021View on GitHub ↗

spatie/commonmark-shiki-highlighter holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (69/100) and lowest on Security (21/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

SpatieOrganization
3,887 followers534 public repossince May 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistspatie/commonmark-shiki-highlighter2.5.2331,05213331 days agospatiecommonmark-shiki-highlighter

Metrics by category

Vitality

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

54Moderate · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
1.4/36Commit cadence — 2/52 weeks with commits
6.3/18Commit volume — 4 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year4
human_commit_share1
days_since_last_push0
active_weeks_last_year2
How it's scored
27/27Ships releases — 13 releases published
16.2/36Release recency — latest release 331 days ago
12.6/27Release cadence — a release every ~177.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count13
latest_release_tag2.5.2
releases_from_tagsno
days_since_latest_release331
mean_days_between_releases177.5

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

61Moderate · 17% of overall
How it's scored
31.8/60Stars — 92 stars
9.6/25Forks — 15 forks
0/15Watchers — 1 watchers
Inputs used
forks15
stars92
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
73.6/80Monthly downloads — 331,052 downloads/month across packagist
6.7/20Registry dependents — 9 packages depend on it
Inputs used
packagesspatie/commonmark-shiki-highlighter
dependents9
ecosystemspackagist
total_downloads5,079,006
monthly_downloads331,052
unverified_packages_excluded—

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.1/22.5Commit distribution — top contributor authored 55% of commits
13.5/13.5Contributor breadth — 13 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled13
top_contributor_share0.549
How it's scored
0/42Issue resolution — no issues or no data
24/30PR acceptance — 12/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs12
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs3
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 3,887 followers of spatie
25/25Track record — 534 public repos, account ~12 yr old
Inputs used
followers3,887
owner_typeOrganization
is_verifiedno
owner_loginspatie
public_repos534
account_age_days4,548
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
26/35Publish recency — latest publish 331 days ago
20/20Version history — 13 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesspatie/commonmark-shiki-highlighter
ecosystemspackagist
any_deprecatedno
min_days_since_publish331

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
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://freek.dev/2024-how-to-render-markdown-with-perfectly-highlighted-code-snippets
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsphp, syntax-highlighting, commonmark
has_wikino
homepagehttps://freek.dev/2024-how-to-render-markdown-with-perfectly-highlighted-code-snippets
docs_sitehttps://freek.dev/2024-how-to-render-markdown-with-perfectly-highlighted-code-snippets
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestscomposer.json, package.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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
advisories1
affected_packages1
assessed_packages39
unassessed_packages8
affected_by_severitymoderate 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 39 resolved dependencies against OSV. 8 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

36Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://code.visualstudio.com/llms.txt)
9.1/40Legible commit history — 14 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://code.visualstudio.com/llms.txt
legible_history_share0.171
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
2.4/10Demonstrated agent practice — 1 of the last 82 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.012
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/6 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes4,408
source_files_sampled6
oversized_source_files0

Key facts

92GitHub stars
13contributors
4commits, last 12 months
0days since last push
13releases
1bus factor
0open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/spatie/commonmark-shiki-highlighter: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-10-22T15:09:09Z. Please include `AF1E:0B65:3B770E:63165D:6ADA2712` when reporting this issue.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
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.

3581013151532021-072023-092025-11
Major 2Minor 6Patch 4

Each point covers 4 days.

Direct dependencies 4
RegistryPackageVersion constraintManifest
Packagistleague/commonmark^2.4.2composer.json
Packagistspatie/shiki-php^2.2.2composer.json
Packagistsymfony/process^5.4|^6.4|^7.1|^8.0composer.json
npmshiki^1.22.2package.json
All dependencies 47

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

RegistryPackageVersionRelation
npmshiki1.22.2direct
Packagistleague/commonmark—direct
Packagistspatie/shiki-php—direct
Packagistsymfony/process—direct
npm@shikijs/core1.22.2indirect
npm@shikijs/engine-javascript1.22.2indirect
npm@shikijs/engine-oniguruma1.22.2indirect
npm@shikijs/types1.22.2indirect
npm@shikijs/vscode-textmate9.3.0indirect
npm@types/hast3.0.4indirect
npm@types/mdast4.0.4indirect
npm@types/unist3.0.3indirect
npm@ungap/structured-clone1.2.0indirect
npmccount2.0.1indirect
npmcharacter-entities-html42.1.0indirect
npmcharacter-entities-legacy3.0.0indirect
npmcomma-separated-tokens2.0.3indirect
npmdequal2.0.3indirect
npmdevlop1.1.0indirect
npmhast-util-to-html9.0.3indirect
npmhast-util-whitespace3.0.0indirect
npmhtml-void-elements3.0.0indirect
npmmdast-util-to-hast13.2.0indirect
npmmicromark-util-character2.1.0indirect
npmmicromark-util-encode2.0.0indirect
npmmicromark-util-sanitize-uri2.0.0indirect
npmmicromark-util-symbol2.0.0indirect
npmmicromark-util-types2.0.0indirect
npmoniguruma-to-js0.4.3indirect
npmproperty-information6.5.0indirect
npmregex4.4.0indirect
npmspace-separated-tokens2.0.2indirect
npmstringify-entities4.0.4indirect
npmtrim-lines3.0.1indirect
npmunist-util-is6.0.0indirect
npmunist-util-position5.0.0indirect
npmunist-util-stringify-position4.0.0indirect
npmunist-util-visit5.0.0indirect
npmunist-util-visit-parents6.0.1indirect
npmvfile6.0.3indirect
npmvfile-message4.0.2indirect
npmzwitch2.0.4indirect
Packagistfriendsofphp/php-cs-fixer—indirect
Packagistphp—indirect
Packagistphpunit/phpunit—indirect
Packagistspatie/phpunit-snapshot-assertions—indirect
Packagistspatie/ray—indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 39 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 8 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
mdast-util-to-hast13.2.0indirectmoderate113.2.1

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 — Packagist.