Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-03 05:07 UTC

lpsinger / ligo.skymap

Localization of gravitational-wave transients. Mirror of https://git.ligo.org/lscsoft/ligo.skymap

Python · CCustom license★ 31 stars⑂ 19 forkssince Mar 2018View on GitHub ↗
KindCommand-line toolPluginLibraryhow this is determined

lpsinger/ligo.skymap holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (73/100) and lowest on AI Readiness (34/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Leo SingerPersonal account
137 followers338 public repossince Apr 2011NASA Goddard Space Flight Center

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 publish
PyPIligo.skymap2.5.436,649164118 days ago

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
10.4/36Commit cadence — 15/52 weeks with commits
18/18Commit volume — 99 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_year99
human_commit_share1
days_since_last_push0
active_weeks_last_year15
How it's scored
16.2/27Ships releases — 76 version tags (no GitHub releases)
27/36Release recency — latest release 118 days ago
19.8/27Release cadence — a release every ~53.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count76
latest_release_tagv2.5.4
releases_from_tagsyes
days_since_latest_release118
mean_days_between_releases53.6
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?

56Moderate · 17% of overall
How it's scored
24/60Stars — 31 stars
10.5/25Forks — 19 forks
2.7/15Watchers — 4 watchers
Inputs used
forks19
stars31
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
60.9/80Monthly downloads — 36,649 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesligo.skymap
dependents—
ecosystemspypi
total_downloads—
monthly_downloads36,649
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.974
How it's scored
42/42Issue resolution — 100% of issues closed
7.5/30PR acceptance — 2/8 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues0
closed_issues24
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs6
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.4/25Owner reach — 137 followers of lpsinger
25/25Track record — 338 public repos, account ~15 yr old
Inputs used
followers137
owner_typeUser
is_verified—
owner_loginlpsinger
public_repos338
account_age_days5,651
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 118 days ago
20/20Version history — 164 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesligo.skymap
ecosystemspypi
any_deprecatedno
min_days_since_publish118

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://lscsoft.docs.ligo.org/ligo.skymap
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsligo, gravitational-waves, astrophysics, gravity, black-hole, neutron-star
has_wikino
homepage—
docs_sitehttps://lscsoft.docs.ligo.org/ligo.skymap
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file 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 — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. 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_packages61
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:ligo.skymap@2.5.4 runtime dependency closure — what installing the published package pulls in — 61 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.

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)
1.1/40Legible commit history — 2 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.02
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — tox.ini
0/11Static type checking
0/10Reproducible environment
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
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
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/138 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes50,590
source_files_sampled138
oversized_source_files0

Key facts

31GitHub stars
10contributors
99commits, last 12 months
0days since last push
76releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'ligo.skymap.core' from its registry

More detail

Star and fork history 0 ★ / 19 ⇿
0Stars
19Forks
50Releases

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.

0481216201922019-042022-122026-09
Major 2Minor 11Patch 37

Each point covers 7 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-10-03 05:07 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
PyPIastroplan>=0.7pyproject.toml
PyPIastropy>=7.0.0pyproject.toml
PyPIastropy-healpix>=0.3pyproject.toml
PyPIhealpy—pyproject.toml
PyPIh5py—pyproject.toml
PyPIigwn-ligolw—pyproject.toml
PyPIigwn-segments—pyproject.toml
PyPIlalsuite>=7.26pyproject.toml
PyPIligo-gracedb>=2.0.1pyproject.toml
PyPImatplotlib>=3.9.1pyproject.toml
PyPInetworkx—pyproject.toml
PyPInumpy>=2.2.0pyproject.toml
PyPIpillow>=2.5.0pyproject.toml
PyPIpytz—pyproject.toml
PyPIreproject>=0.3.2pyproject.toml
PyPIscipy>=1.10.1pyproject.toml
PyPIshapely>=2.0.0pyproject.toml
PyPItqdm>=4.27.0pyproject.toml
All dependencies 18

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

RegistryPackageVersionRelation
PyPIastroplan—direct
PyPIastropy—direct
PyPIastropy-healpix—direct
PyPIlalsuite—direct
PyPIligo-gracedb—direct
PyPImatplotlib—direct
PyPInumpy—direct
PyPIpillow—direct
PyPIreproject—direct
PyPIscipy—direct
PyPIshapely—direct
PyPItqdm—direct
PyPIfigaro—indirect
PyPIsetuptools—indirect
PyPIsetuptools-scm—indirect
PyPIsphinx—indirect
PyPIsphinx-argparse—indirect
PyPIsphinxcontrib-mermaid—indirect
Dependency advisories 0

Installing pypi:ligo.skymap@2.5.4 pulls in 61 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.