Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 06:24 UTC

citation-style-language / locales

Official repository for Citation Style Language (CSL) locale files.

Python · RubyNo license detected★ 170 stars⑂ 246 forkssince Feb 2011View on GitHub ↗

citation-style-language/locales holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on AI Readiness (34/100). It was last updated 6 days ago. 5 contributors account 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

357 followers25 public repossince Dec 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistcitation-style-language/localesv0.0.10140,97110114 days ago

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
21.5/36Commit cadence — 31/52 weeks with commits
18/18Commit volume — 112 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year112
human_commit_share1
days_since_last_push6
active_weeks_last_year31

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.0.104
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases8
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
36.1/60Stars — 170 stars
19.9/25Forks — 246 forks
7/15Watchers — 19 watchers
Inputs used
forks246
stars170
watchers19
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
61.5/80Monthly downloads — 40,971 downloads/month across packagist
7.6/20Registry dependents — 13 packages depend on it
Inputs used
packagescitation-style-language/locales
dependents13
ecosystemspackagist
total_downloads939,821
monthly_downloads40,971
unverified_packages_excluded—

Sustainability & Governance

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

83Excellent · 23% of overall
How it's scored
45.9/54Bus factor — 5 contributor(s) cover half of all commits
17.5/22.5Commit distribution — top contributor authored 22% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled99
top_contributor_share0.223
How it's scored
35.4/42Issue resolution — 84% of issues closed
24.1/30PR acceptance — 297/369 decided PRs merged
9.3/13Newcomer PR acceptance — 5/7 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 6/13 approved changesets -- score normalized to 4
Inputs used
merged_prs297
open_issues11
closed_issues59
prs_merged_7d2
prs_decided_7d2
prs_merged_30d8
prs_decided_30d10
issue_closed_ratio0.843
closed_unmerged_prs72
first_time_authors_30d6
first_time_prs_merged_30d5
first_time_prs_decided_30d7
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
18.4/25Owner reach — 357 followers of citation-style-language
22.3/25Track record — 25 public repos, account ~15 yr old
Inputs used
followers357
owner_typeOrganization
is_verifiedno
owner_logincitation-style-language
public_repos25
account_age_days5,753

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 14 days ago
20/20Version history — 101 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescitation-style-language/locales
ecosystemspackagist
any_deprecatedno
min_days_since_publish14

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://citationstyles.org/
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicscitation-style-language, hacktoberfest, csl
has_wikiyes
homepagehttps://citationstyles.org/
docs_sitehttps://citationstyles.org/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 6/13 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 12 contributing companies or organizations
0/10Dangerous-Workflow — dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: nokogiri 1.18.9 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 210 days ago
Inputs used
sourceosv
advisories16
affected_packages5
assessed_packages42
unassessed_packages0
affected_by_severityhigh 4, low 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 42 resolved dependencies against OSV. 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.6/40Legible commit history — 48 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.48
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
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes12,497
source_files_sampled5
oversized_source_files0

Key facts

170GitHub stars
99contributors
112commits, last 12 months
6days since last push
100releases
5bus factor
11open issues
Packagist, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 246 ⇿
0Stars
246Forks
95Releases

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.

05010015020025024262011-042018-122026-09
Major 0Minor 0Patch 95

Each point covers 15 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-17 06:23 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 6/13 approved changesets -- score normalized to 4
10Contributorsproject has 12 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
RubyGemsrake—Gemfile
RubyGemsrspec—Gemfile
RubyGemsnokogiri—Gemfile
RubyGemscsl~>2.2.1Gemfile
RubyGemsfuubar—Gemfile
RubyGemssheldon—Gemfile
All dependencies 42

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

RegistryPackageVersionRelation
RubyGemscsl2.1.0direct
RubyGemsfuubar2.5.1direct
RubyGemsnokogiri1.18.9direct
RubyGemsrake13.0.6direct
RubyGemsrspec3.10.0direct
RubyGemsaddressable2.8.7indirect
RubyGemsciteproc1.1.0indirect
RubyGemsciteproc-ruby2.1.1indirect
RubyGemscsl-styles2.0.1indirect
RubyGemsdate3.4.1indirect
RubyGemsdiff-lcs1.5.0indirect
RubyGemsdiffy3.4.3indirect
RubyGemsdotenv3.1.8indirect
RubyGemserubis2.7.0indirect
RubyGemsfaraday1.0.1indirect
RubyGemsfaraday_middleware1.2.0indirect
RubyGemsforwardable1.3.3indirect
RubyGemsgit_diff0.4.3indirect
RubyGemshashdiff0.3.7indirect
RubyGemsjson2.10.2indirect
RubyGemsmini_portile22.8.9indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsnamae1.2.0indirect
RubyGemsobserver0.1.2indirect
RubyGemsoctokit4.25.1indirect
RubyGemsopen-uri0.5.0indirect
RubyGemsostruct0.6.1indirect
RubyGemspublic_suffix6.0.1indirect
RubyGemsracc1.8.1indirect
RubyGemsreverse_markdown3.0.0indirect
RubyGemsrexml3.4.2indirect
RubyGemsrspec-core3.10.1indirect
RubyGemsrspec-expectations3.10.1indirect
RubyGemsrspec-mocks3.10.2indirect
RubyGemsrspec-support3.10.3indirect
RubyGemsruby-progressbar1.11.0indirect
RubyGemssawyer0.9.2indirect
RubyGemsset1.1.1indirect
RubyGemssingleton0.3.0indirect
RubyGemsstringio3.1.6indirect
RubyGemstime0.4.1indirect
RubyGemsuri1.0.3indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 42 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
nokogiri1.18.9directhigh111.19.4
addressable2.8.7indirecthigh12.9.0
faraday1.0.1indirecthigh22.14.3
uri1.0.3indirecthigh11.0.4
json2.10.2indirectlow12.19.9

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.