Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 12:16 UTC

pygments / pygments

Pygments is a generic syntax highlighter written in Python

PythonBSD-2-Clause★ 2,188 stars⑂ 836 forkssince Aug 2019View on GitHub ↗
KindLibraryhow this is determined
#python#syntax-highlighting

pygments/pygments holds a health index of 75 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 today. 2 contributors account for most of its recent work.

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

75
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 65 is calibrated to 75 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.20.0-68108 days agosyntaxhighlighting

Metrics by category

Vitality

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

80Excellent · 21% of overall

Development activity

78Good
How it's scored
36/36Push recency — last push 0 days ago
15.9/36Commit cadence — 23/52 weeks with commits
18/18Commit volume — 221 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year221
human_commit_share—
days_since_last_push0
active_weeks_last_year23

Release discipline

82Excellent
How it's scored
27/27Ships releases — 36 releases published
27/36Release recency — latest release 108 days ago
19.8/27Release cadence — a release every ~107.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count36
latest_release_tag2.20.0
releases_from_tagsno
days_since_latest_release108
mean_days_between_releases107.3

Community & Adoption

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

70Good · 17% of overall

Popularity & adoption

87Excellent
How it's scored
54.2/60Stars — 2,188 stars
24.4/25Forks — 836 forks
8.7/15Watchers — 37 watchers
Inputs used
forks836
stars2,188
watchers37
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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

77Good · 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 39% of commits
13.5/13.5Contributor breadth — 100 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.386

Issue & PR responsiveness

82Excellent
How it's scored
32.9/42Issue resolution — 78% of issues closed
26.1/30PR acceptance — 924/1,061 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_prs924
open_issues421
closed_issues1,518
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.783
closed_unmerged_prs137
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.

Ownership & stewardship

77Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
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_verified—
owner_loginpygments
public_repos7
account_age_days2,611
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

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 — 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 — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements.txt
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

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

Agent context & guidance

1Critical
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.

Verify loop (build / test / typecheck)

71Good
How it's scored
18/18One-command bootstrap — doc/Makefile, tests/examplefiles/make/Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
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_share—
toolchain_manifests—
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

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,903
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,188GitHub stars
100contributors
221commits, last 12 months
0days since last push
36releases
2bus factor
421open issues
PyPIpackage ecosystems

Data collection warnings

  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

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
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 →

100streamlit/streamlitStreamlit — A faster way to build and share data apps.Exceptional100PrefectHQ/prefectPrefect is a workflow orchestration framework for building resilient data pipelines in Python.Exceptional100open-telemetry/opentelemetry-pythonOpenTelemetry Python API and SDK Exceptional100reflex-dev/reflex🕸️ Web apps in pure Python 🐍Exceptional100optuna/optunaA hyperparameter optimization frameworkExceptional100python-pillow/PillowPython Imaging Library (fork)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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.