Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 20:36 UTC

SanPen / VeraGrid

VeraGrid, a cross-platform power systems software written in Python with user interface, used in academia and industry.

PythonMPL-2.0★ 600 stars⑂ 133 forkssince Jan 2016View on GitHub ↗
KindDesktop applicationCommand-line toolLibraryhow this is determined

SanPen/VeraGrid holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Security (30/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Santiago Peñate VeraPersonal account
189 followers26 public repossince Jul 2015eRoots

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIVeraGrid6.5.17-1461 day agopowersystemsplanning
PyPIVeraGridEngine6.5.17-1471 day agopowersystemsplanning
PyPIVeraGridServer6.5.17-1461 day agopowersystemsplanning

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 recencylast push 2 days ago
28.4/36Commit cadence41/52 weeks with commits
18/18Commit volume207 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year207
human_commit_share0.97
days_since_last_push2
active_weeks_last_year41
How it's scored
27/27Ships releases33 releases published
36/36Release recencylatest release 15 days ago
19.8/27Release cadencea release every ~84.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count33
latest_release_tagv6.5.0
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases84.3

Community & Adoption

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

74Good · 17% of overall
How it's scored
45.1/60Stars600 stars
17.7/25Forks133 forks
8.6/15Watchers36 watchers
Inputs used
forks133
stars600
watchers36
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MPL-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io, travis-ci.org, www.bestpractices.dev
has_pull_request_templateyes

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.6/22.5Commit distributiontop contributor authored 71% of commits
13.5/13.5Contributor breadth33 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled33
top_contributor_share0.707
How it's scored
40.6/42Issue resolution97% of issues closed
22.6/30PR acceptance120/159 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs120
open_issues10
closed_issues295
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.967
closed_unmerged_prs39
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
16.4/25Owner reach189 followers of SanPen
22.4/25Track record26 public repos, account ~11 yr old
Inputs used
followers189
owner_typeUser
is_verified
owner_loginSanPen
public_repos26
account_age_days4,065
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on pypi
35/35Publish recencylatest publish 1 days ago
20/20Version history147 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesVeraGrid, VeraGridEngine, VeraGridServer
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.pylintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno 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 sitehttps://eroots.tech/veragrid-gslv
10/10Repository description
10/10Topics18 topics
10/10Wiki
Inputs used
topicspython, powerflow, electrical-engineering, electrical, helm, newton-raphson, latin-hypercube, monte-carlo-simulation, cim, comon-information-model, stochastic-power-flow, multi-terminal, acdc, optimization, power-systems, emt, rms, small-signal-stability
has_wikiyes
homepagehttps://eroots.tech/veragrid-gslv
docs_sitehttps://eroots.tech/veragrid-gslv
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

30At Risk · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestsdoc/requirements.txt, requirements.txt, setup.py
has_codeql_workflowno
has_security_policyyes
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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
2.2/40Legible commit history4 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.041
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdoc/Makefile, src/tests/data/grids/CGMES_3_0/Relicap/Makefile
22/22Automated tests
11/11Lint / format config.pylintrc
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesdoc/Makefile, src/tests/data/grids/CGMES_3_0/Relicap/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable codePython without a type-check config
52.6/55Manageable file sizes151/3,477 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes1,534,900
source_files_sampled3,477
oversized_source_files151
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

600GitHub stars
33contributors
207commits, last 12 months
2days since last push
33releases
1bus factor
10open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'VeraGrid-doc-meta' from its registry
  • pypi download statistics for 'VeraGrid' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • pypi download statistics for 'VeraGridEngine' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • pypi download statistics for 'VeraGridServer' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • deps.dev does not index pypi:VeraGrid@6.5.17; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/05 20:34:42 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 133 ⇿
0Stars
133Forks
32Releases

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.

025507510012515013142016-032021-062026-08
Major 1Minor 13Patch 15

Each point covers 10 days.

All dependencies 47

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

RegistryPackageVersionRelation
PyPIautogradindirect
PyPIbrotliindirect
PyPIchardetindirect
PyPIcryptographyindirect
PyPIfastapiindirect
PyPIfastparquetindirect
PyPIfmpyindirect
PyPIgeopyindirect
PyPIh11indirect
PyPIh5pyindirect
PyPIhighspyindirect
PyPIidnaindirect
PyPIlinkify-it-pyindirect
PyPImatplotlibindirect
PyPImyst-parserindirect
PyPInetworkxindirect
PyPInumbaindirect
PyPInumpyindirect
PyPIopencv-pythonindirect
PyPIopenpyxlindirect
PyPIpackagingindirect
PyPIpandasindirect
PyPIpillowindirect
PyPIpsycopgindirect
PyPIpulpindirect
PyPIpvlibindirect
PyPIpyarrowindirect
PyPIpygmentsindirect
PyPIpymooindirect
PyPIpyprojindirect
PyPIpyside6indirect
PyPIpytablewriterindirect
PyPIpytestindirect
PyPIrdflibindirect
PyPIrequestsindirect
PyPIscikit-learnindirect
PyPIscipyindirect
PyPIsphinxindirect
PyPIsphinx-rtd-themeindirect
PyPItablesindirect
PyPIurllib3indirect
PyPIuvicornindirect
PyPIveragridengineindirect
PyPIwebsocketsindirect
PyPIwindpowerlibindirect
PyPIxlrdindirect
PyPIxlwtindirect
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.

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.