Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 21:40 UTC

Nixtla / coreforecast

Fast implementations of common forecasting routines

Python · C++Apache-2.0★ 42 stars⑂ 11 forkssince Oct 2023View on GitHub ↗

Nixtla/coreforecast holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on Vitality (59/100). It was last updated 31 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

NixtlaOrganization · verified domain
2,845 followers40 public repossince Mar 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIcoreforecast0.0.181,935,9082049 days agoforecastingtime-series

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
18/36Push recencylast push 31 days ago
4.2/36Commit cadence6/52 weeks with commits
11.5/18Commit volume18 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year18
human_commit_share0.62
days_since_last_push31
active_weeks_last_year6
How it's scored
27/27Ships releases19 releases published
36/36Release recencylatest release 49 days ago
19.8/27Release cadencea release every ~83.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count19
latest_release_tagv0.0.18
releases_from_tagsno
days_since_latest_release49
mean_days_between_releases83.9
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?

63Moderate · 17% of overall
How it's scored
26.2/60Stars42 stars
8.3/25Forks11 forks
2.7/15Watchers4 watchers
Inputs used
forks11
stars42
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads1,935,908 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagescoreforecast
dependents
ecosystemspypi
total_downloads
monthly_downloads1,935,908
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?

76Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.9/22.5Commit distributiontop contributor authored 78% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.78
How it's scored
38.5/42Issue resolution92% of issues closed
24/30PR acceptance99/124 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-ReviewFound 15/16 approved changesets -- score normalized to 9
Inputs used
merged_prs99
open_issues1
closed_issues11
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.917
closed_unmerged_prs25
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
24.8/25Owner reach2,845 followers of Nixtla
22.7/25Track record40 public repos, account ~5 yr old
Inputs used
followers2,845
owner_typeOrganization
is_verifiedyes
owner_loginNixtla
public_repos40
account_age_days2,003

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 49 days ago
20/20Version history20 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagescoreforecast
ecosystemspypi
any_deprecatedno
min_days_since_publish49

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests20 out of 30 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://nixtlaverse.nixtla.io/coreforecast
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://nixtlaverse.nixtla.io/coreforecast
docs_sitehttps://nixtlaverse.nixtla.io/coreforecast
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

71Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.5/2.5CI-Tests20 out of 30 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-ReviewFound 15/16 approved changesets -- score normalized to 9
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
3/5SASTSAST tool is not run on all commits -- score normalized to 6
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.4
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_packages1
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 pypi:coreforecast@0.0.18 runtime dependency closure — what installing the published package pulls in — 1 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
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://nixtlaverse.nixtla.io/llms.txt)
40/40Legible commit history49 of 62 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://nixtlaverse.nixtla.io/llms.txt
legible_history_share0.79
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance38 of the last 100 commits are automated dependency updates
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.38
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/42 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes37,122
source_files_sampled42
oversized_source_files0

Key facts

42GitHub stars
7contributors
18commits, last 12 months
31days since last push
19releases
1bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-01-31: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 42 stars today.

More detail

Star and fork history 42 ★ / 11 ⇿
42Stars
11Forks
18Releases

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.

Star history is shown as collected on 2026-01-31. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01020304050421172023-102025-012026-04
Major 0Minor 0Patch 17

Each point covers 3 days.

OpenSSF Scorecard 6.4 / 10
6.4aggregate

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-08-27 21:40 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests20 out of 30 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 15/16 approved changesets -- score normalized to 9
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
6SASTSAST tool is not run on all commits -- score normalized to 6
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPInumpy>=1.20.0pyproject.toml
All dependencies 43

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

RegistryPackageVersionRelation
PyPInumpy2.2.6direct
PyPInumpy2.4.0direct
PyPIcffi2.0.0indirect
PyPIcfgv3.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoreforecast0.0.18indirect
PyPIcoverage7.13.1indirect
PyPIdistlib0.4.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfilelock3.20.3indirect
PyPIgriffe1.15.0indirect
PyPIgriffe2md1.2.6indirect
PyPIidentify2.6.15indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown-it-py4.0.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdformat1.0.0indirect
PyPImdurl0.1.2indirect
PyPImkdocstrings-parser0.0.1indirect
PyPInodeenv1.10.0indirect
PyPIpackaging25.0indirect
PyPIpandas2.3.3indirect
PyPIpip-licenses5.5.0indirect
PyPIplatformdirs4.5.1indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.5.1indirect
PyPIprettytable3.17.0indirect
PyPIpycparser2.23indirect
PyPIpygments2.20.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-codspeed4.2.0indirect
PyPIpytest-cov7.0.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytz2025.2indirect
PyPIpyyaml6.0.3indirect
PyPIrich14.2.0indirect
PyPIsix1.17.0indirect
PyPItomli2.3.0indirect
PyPItyping-extensions4.15.0indirect
PyPItzdata2025.3indirect
PyPIvirtualenv20.36.1indirect
PyPIwcwidth0.2.14indirect
Dependency advisories 0

Installing pypi:coreforecast@0.0.18 pulls in 1 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.34.0 — full methodology · metrics wiki.

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