Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 03:56 UTC

pygments / pygments

Pygments is a generic syntax highlighter written in Python

PythonBSD-2-Clause★ 2,207 stars⑂ 879 forkssince Aug 2019View on GitHub ↗
KindCommand-line toolLibraryhow this is determined
#python#syntax-highlighting

pygments/pygments holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (88/100) and lowest on Security (1/100). It was last updated 22 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

pygmentsOrganization
58 followers7 public repossince May 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIPygments2.21.01,089,023,7166922 days agosyntaxhighlighting

Metrics by category

Vitality

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

74Good · 21% of overall

Development activity

68Good
How it's scored
28.8/36Push recency — last push 22 days ago
14.5/36Commit cadence — 21/52 weeks with commits
18/18Commit volume — 214 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year214
human_commit_share1
days_since_last_push22
active_weeks_last_year21

Release discipline

84Excellent
How it's scored
27/27Ships releases — 37 releases published
36/36Release recency — latest release 22 days ago
12.6/27Release cadence — a release every ~123 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count37
latest_release_tag2.21.0
releases_from_tagsno
days_since_latest_release22
mean_days_between_releases123

Community & Adoption

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

78Good · 17% of overall

Popularity & adoption

88Excellent
How it's scored
54.2/60Stars — 2,207 stars
24.5/25Forks — 879 forks
8.8/15Watchers — 39 watchers
Inputs used
forks879
stars2,207
watchers39
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno

Ecosystem adoption (downloads)

100Exceptional
How it's scored
80/80Monthly downloads — 1,089,023,716 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesPygments
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,089,023,716
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?

70Good · 23% of overall

Maintainer resilience (bus factor)

58Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.8/22.5Commit distribution — top contributor authored 38% of commits
13.5/13.5Contributor breadth — 100 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.385

Issue & PR responsiveness

69Good
How it's scored
32.7/42Issue resolution — 78% of issues closed
26.1/30PR acceptance — 928/1,067 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs928
open_issues431
closed_issues1,518
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.779
closed_unmerged_prs139
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1

Ownership & stewardship

61Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.7/25Owner reach — 58 followers of pygments
18.6/25Track record — 7 public repos, account ~7 yr old
Inputs used
followers58
owner_typeOrganization
is_verifiedno
owner_loginpygments
public_repos7
account_age_days2,666

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 22 days ago
20/20Version history — 69 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesPygments
ecosystemspypi
any_deprecatedno
min_days_since_publish22

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall

Engineering practices

80Excellent
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff]), tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — http://pygments.org/
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicspython, syntax-highlighting
has_wikiyes
homepagehttp://pygments.org/
docs_sitehttp://pygments.org/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

1Critical · 16% of overall

Security posture

1Critical
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements.txt
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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.

58Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 76 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.76
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

57Moderate
How it's scored
18/18One-command bootstrap — doc/Makefile, tests/examplefiles/make/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff]), tox.ini
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdoc/Makefile, tests/examplefiles/make/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

53Moderate
How it's scored
0/45Type-checkable code — Python without a type-check config
53/55Manageable file sizes — 17/479 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes157,900
source_files_sampled479
oversized_source_files17

Machine-readable interfaces

100Exceptional
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — tests/examplefiles/graphql/ex01_field1.graphql, tests/examplefiles/graphql/ex02_field2.graphql, tests/examplefiles/graphql/ex03_arguments1.graphql, tests/examplefiles/graphql/ex04_arguments2.graphql, tests/examplefiles/graphql/ex05_aliases.graphql, tests/examplefiles/graphql/ex06_fragments1.graphql, tests/examplefiles/graphql/ex07_fragments2.graphql, tests/examplefiles/graphql/ex08_operation_name.graphql, tests/examplefiles/graphql/ex09_variables1.graphql, tests/examplefiles/graphql/ex10_variables2.graphql, tests/examplefiles/graphql/ex11_directives.graphql, tests/examplefiles/graphql/ex12_mutations.graphql, tests/examplefiles/graphql/ex13_inline_fragments1.graphql, tests/examplefiles/graphql/ex14_inline_fragments2.graphql, tests/examplefiles/protobuf/addressbook.proto
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filestests/examplefiles/graphql/ex01_field1.graphql, tests/examplefiles/graphql/ex02_field2.graphql, tests/examplefiles/graphql/ex03_arguments1.graphql, tests/examplefiles/graphql/ex04_arguments2.graphql, tests/examplefiles/graphql/ex05_aliases.graphql, tests/examplefiles/graphql/ex06_fragments1.graphql, tests/examplefiles/graphql/ex07_fragments2.graphql, tests/examplefiles/graphql/ex08_operation_name.graphql, tests/examplefiles/graphql/ex09_variables1.graphql, tests/examplefiles/graphql/ex10_variables2.graphql, tests/examplefiles/graphql/ex11_directives.graphql, tests/examplefiles/graphql/ex12_mutations.graphql, tests/examplefiles/graphql/ex13_inline_fragments1.graphql, tests/examplefiles/graphql/ex14_inline_fragments2.graphql, tests/examplefiles/protobuf/addressbook.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

2,207GitHub stars
100contributors
214commits, last 12 months
22days since last push
37releases
2bus factor
431open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 879 ⇿
0Stars
879Forks
37Releases

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.

02004006008001,000863432019-102023-032026-09
Major 0Minor 18Patch 19

Each point covers 7 days.

All dependencies 6

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

RegistryPackageVersionRelation
PyPIcolorama—indirect
PyPIhatchling—indirect
PyPIliteral-string-interpol—indirect
PyPIsystemd—indirect
PyPItext-whitespace—indirect
PyPItox—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with pygments/pygments. Read them side by side →

100aws/aws-sam-cliCLI tool to build, test, debug, and deploy Serverless applications using AWS SAMExceptional100numpy/numpyThe fundamental package for scientific computing with Python.Exceptional100astropy/astropyAstronomy and astrophysics core libraryExceptional100huggingface/transformers🤗 Transformers: the model-definition framework for state-of-the-art machine learning models in text, vision, audio, and multimodal models, for both inference and training. Exceptional100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional100deepset-ai/haystackOpen-source AI orchestration framework for building context-engineered, production-ready LLM applications. Design modular pipelines and agent workflows with explicit control over retrieval, routing, memory, and generation. Built for scalable agents, RAG, multimodal applications, semantic search, and conversational systems.Exceptional

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