Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 04:15 UTC

AntaresSimulatorTeam / GemsPy

Gems, a framework for generic modelling in energy systems

PythonMPL-2.0★ 19 stars⑂ 4 forkssince Feb 2024View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

AntaresSimulatorTeam/GemsPy holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (44/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

29 followers34 public repossince Jul 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIgemspy0.3.02,6301116 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 2 days ago
22.8/36Commit cadence — 33/52 weeks with commits
18/18Commit volume — 106 commits in the last year
10/10OpenSSF Scorecard: Maintained — 28 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year106
human_commit_share1
days_since_last_push2
active_weeks_last_year33

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 10 releases published
36/36Release recency — latest release 16 days ago
27/27Release cadence — a release every ~29.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tagv0.3.0
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases29.2
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?

44Weak · 17% of overall
How it's scored
20.4/60Stars — 19 stars
4/25Forks — 4 forks
0/15Watchers — 0 watchers
Inputs used
forks4
stars19
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MPL-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateyes
How it's scored
45.6/80Monthly downloads — 2,630 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgemspy
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,630
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.8/22.5Commit distribution — top contributor authored 34% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor2
contributors_sampled18
top_contributor_share0.343
How it's scored
28.4/42Issue resolution — 68% of issues closed
24.6/30PR acceptance — 212/259 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs212
open_issues30
closed_issues63
prs_merged_7d1
prs_decided_7d1
prs_merged_30d10
prs_decided_30d11
issue_closed_ratio0.677
closed_unmerged_prs47
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 backing — organization-owned
0/20Verified domain
10.6/25Owner reach — 29 followers of AntaresSimulatorTeam
23.2/25Track record — 34 public repos, account ~8 yr old
Inputs used
followers29
owner_typeOrganization
is_verifiedno
owner_loginAntaresSimulatorTeam
public_repos34
account_age_days3,057

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.black], [tool.isort])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 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 — 30 out of 30 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 28 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 41 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages32
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:gemspy@0.3.0 runtime dependency closure — what installing the published package pulls in — 32 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.

65Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 75 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.75
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes11,552
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.black], [tool.isort])
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
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
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.17
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
54.7/55Manageable file sizes — 1/179 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes65,186
source_files_sampled179
oversized_source_files1

Key facts

19GitHub stars
18contributors
106commits, last 12 months
2days since last push
10releases
2bus factor
30open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
4Releases

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.

1223344412024-022025-032026-04
Major 0Minor 0Patch 4

Each point covers 2 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-11-16 04:14 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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities41 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
PyPInumpy>=1.26pyproject.toml
PyPIantlr4-python3-runtime>=4.13.2pyproject.toml
PyPIPyYAML>=6.0.2pyproject.toml
PyPIpydantic>=2.0pyproject.toml
PyPIanytree>=2.13pyproject.toml
PyPIlinopy>=0.9.0pyproject.toml
PyPIxarray>=2025.3pyproject.toml
PyPIhighspy>=1.14pyproject.toml
PyPIpandas>=2.2pyproject.toml
PyPIattrs>=26.0pyproject.toml
PyPIpyarrow>=15.0pyproject.toml
All dependencies 93

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

RegistryPackageVersionRelation
PyPIantlr4-python3-runtime4.13.2direct
PyPIanytree2.13.0direct
PyPIattrs26.1.0direct
PyPIhighspy1.14.0direct
PyPIlinopy0.9.0direct
PyPInumpy2.4.4direct
PyPIpandas3.0.2direct
PyPIpyarrow24.0.0direct
PyPIpydantic2.12.5direct
PyPIpyyaml6.0.3direct
PyPIxarray2026.2.0direct
PyPIannotated-types0.7.0indirect
PyPIantlr4-tools0.2.2indirect
PyPIbabel2.18.0indirect
PyPIbackrefs6.2indirect
PyPIblack26.3.1indirect
PyPIbottleneck1.6.0indirect
PyPIcertifi2026.2.25indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIclick8.3.2indirect
PyPIcloudpickle3.1.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.5indirect
PyPIdask2026.3.0indirect
PyPIdeprecation2.1.0indirect
PyPIdistlib0.4.0indirect
PyPIexecnet2.1.2indirect
PyPIfilelock3.29.0indirect
PyPIfsspec2026.3.0indirect
PyPIgemspy0.3.0indirect
PyPIghp-import2.1.0indirect
PyPIgriffelib2.0.2indirect
PyPIgurobipy13.0.2indirect
PyPIidentify2.6.19indirect
PyPIidna3.11indirect
PyPIimportlib-metadata9.0.0indirect
PyPIiniconfig2.3.0indirect
PyPIinstall-jdk1.1.0indirect
PyPIisort8.0.1indirect
PyPIjinja23.1.6indirect
PyPIlibrt0.9.0indirect
PyPIlocket1.0.0indirect
PyPImarkdown3.10.2indirect
PyPImarkupsafe3.0.3indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.6indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImkdocstrings1.0.4indirect
PyPImkdocstrings-python2.0.3indirect
PyPImypy1.20.2indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.10.0indirect
PyPInumexpr2.14.1indirect
PyPIpackaging26.0indirect
PyPIpaginate0.5.7indirect
PyPIpandas-stubs3.0.0.260204indirect
PyPIpartd1.4.2indirect
PyPIpathspec1.1.0indirect
PyPIplatformdirs4.9.6indirect
PyPIpluggy1.6.0indirect
PyPIpolars1.39.3indirect
PyPIpolars-runtime-321.39.3indirect
PyPIpre-commit4.6.0indirect
PyPIpydantic-core2.41.5indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions10.21.2indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-xdist3.8.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-discovery1.2.2indirect
PyPIpytokens0.4.1indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.33.1indirect
PyPIscipy1.17.1indirect
PyPIsix1.17.0indirect
PyPItomli2.4.1indirect
PyPItoolz1.1.0indirect
PyPItqdm4.67.3indirect
PyPItypes-pyyaml6.0.12.20260408indirect
PyPItyping-extensions4.15.0indirect
PyPItyping-inspection0.4.2indirect
PyPItzdata2026.1indirect
PyPIurllib32.6.3indirect
PyPIvirtualenv21.2.4indirect
PyPIwatchdog6.0.0indirect
PyPIxpress9.9.0indirect
PyPIxpresslibs9.9.0indirect
PyPIzipp3.23.0indirect
Dependency advisories 0

Installing pypi:gemspy@0.3.0 pulls in 32 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 statistics — PyPI.