Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-20 04:33 UTC

observatorycontrolsystem / science-archive

Science archive for astronomical data

PythonGPL-3.0★ 2 stars⑂ 3 forkssince Oct 2018View on GitHub ↗
KindNetwork servicehow this is determined

observatorycontrolsystem/science-archive holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Vitality (80/100) and lowest on Community & Adoption (26/100). It was last updated 24 days ago. 2 contributors account for most of its recent work.

59
overall / 100
Moderate

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.

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

Ownership

32 followers20 public repossince Apr 2020

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

Metrics by category

Vitality

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

80Excellent · 21% of overall
How it's scored
28.8/36Push recency — last push 24 days ago
10.4/36Commit cadence — 15/52 weeks with commits
17.2/18Commit volume — 81 commits in the last year
10/10OpenSSF Scorecard: Maintained — 28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year81
human_commit_share1
days_since_last_push24
active_weeks_last_year15

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 20 releases published
36/36Release recency — latest release 45 days ago
27/27Release cadence — a release every ~24.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count20
latest_release_tagv2.8.2
releases_from_tagsno
days_since_latest_release45
mean_days_between_releases24.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?

26At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
2.5/25Forks — 3 forks
2.7/15Watchers — 4 watchers
Inputs used
forks3
stars2
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapp.codacy.com, coveralls.io, github.com
has_pull_request_templateno

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
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.5/22.5Commit distribution — top contributor authored 49% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.488
How it's scored
42/42Issue resolution — 100% of issues closed
25.7/30PR acceptance — 90/105 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 6/21 approved changesets -- score normalized to 2
Inputs used
merged_prs90
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs15
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.9/25Owner reach — 32 followers of observatorycontrolsystem
21.6/25Track record — 20 public repos, account ~6 yr old
Inputs used
followers32
owner_typeOrganization
is_verifiedno
owner_loginobservatorycontrolsystem
public_repos20
account_age_days2,401

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 6 out of 12 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/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_dirno
has_descriptionyes

Security

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

48Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.2/2.5CI-Tests — 6 out of 12 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 6/21 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 28 commit(s) and 0 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 — 31 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
6.6/35Direct dependencies free of known advisories — 4 affected: django 6.0.5 (high 8.8), djangorestframework 3.17.1 (high 7.5), markdown 3.0.1 (high 7.5), +1 more
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
25.1/40No advisories left outstanding — 3 advisory-carrying package(s) unaddressed past 90 days; oldest published 519 days ago
Inputs used
sourceosv
advisories58
affected_packages7
assessed_packages63
unassessed_packages0
affected_by_severityhigh 6, moderate 1
direct_affected_packages4
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 63 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.

30At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.26
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 — Dockerfile, Nix, 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_nixyes
has_testsyes
lockfilespoetry.lock
has_dockerfileyes
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
54.3/55Manageable file sizes — 1/77 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes64,567
source_files_sampled77
oversized_source_files1

Key facts

2GitHub stars
12contributors
81commits, last 12 months
24days since last push
20releases
2bus 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 'science-archive' from its registry

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
1Releases

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.

12233312020-062021-072022-08
Major 0Minor 0Patch 1

Each point covers 2 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-20 04:33 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests6 out of 12 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/21 approved changesets -- score normalized to 2
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 0 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
0Vulnerabilities31 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
PyPIdjango>=6,<6.1pyproject.toml
PyPIpsycopg^3.3.4pyproject.toml
PyPIdjango-filter^25.2pyproject.toml
PyPIdjangorestframework^3.17pyproject.toml
PyPIPyYAML^6.0pyproject.toml
PyPIboto3<2.0pyproject.toml
PyPIastropy>=7,<9.0pyproject.toml
PyPIMarkdown>=3.0,<3.1pyproject.toml
PyPIgunicorn^26.0.0pyproject.toml
PyPIdjango-cors-headers^4.9.0pyproject.toml
PyPIdrf-yasg^1.21pyproject.toml
PyPIpython3-memcached>=1.51,<2.0pyproject.toml
PyPIuritemplate3.0.1pyproject.toml
PyPIkombu^5.6.0pyproject.toml
PyPIocs-authentication>=0.2.4pyproject.toml
PyPIsetuptools-scm^10.0.5pyproject.toml
PyPIrequests^2pyproject.toml
PyPIdjango-extensions^4.1pyproject.toml
PyPIlcogt-logging^0.3.2pyproject.toml
PyPIdjango-redis^6.0.0pyproject.toml
PyPIocs_archive>=0.5.0pyproject.toml
PyPIurllib3<2.0pyproject.toml
PyPIanyascii^0.3.3pyproject.toml
All dependencies 63

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

RegistryPackageVersionRelation
PyPIanyascii0.3.3direct
PyPIastropy7.2.0direct
PyPIboto31.43.13direct
PyPIdjango6.0.5direct
PyPIdjango-cors-headers4.9.0direct
PyPIdjango-extensions4.1direct
PyPIdjango-filter25.2direct
PyPIdjango-redis6.0.0direct
PyPIdjangorestframework3.17.1direct
PyPIdrf-yasg1.21.15direct
PyPIgunicorn26.0.0direct
PyPIkombu5.6.2direct
PyPIlcogt-logging0.3.2direct
PyPImarkdown3.0.1direct
PyPIocs-archive0.5.0direct
PyPIocs-authentication0.2.4direct
PyPIpsycopg3.3.4direct
PyPIpython3-memcached1.51direct
PyPIpyyaml6.0.3direct
PyPIrequests2.34.2direct
PyPIsetuptools-scm10.0.5direct
PyPIuritemplate3.0.1direct
PyPIurllib31.26.20direct
PyPIamqp5.3.1indirect
PyPIasgiref3.11.1indirect
PyPIastropy-iers-data0.2026.5.18.1.11.28indirect
PyPIbotocore1.43.13indirect
PyPIcertifi2026.5.20indirect
PyPIcffi2.0.0indirect
PyPIcharset-normalizer3.4.7indirect
PyPIcoverage6.5.0indirect
PyPIcoveralls3.3.1indirect
PyPIdocopt0.6.2indirect
PyPIfactory-boy3.3.3indirect
PyPIfaker40.18.0indirect
PyPIflake85.0.4indirect
PyPIgevent26.5.0indirect
PyPIgreenlet3.5.1indirect
PyPIidna3.16indirect
PyPIinflection0.5.1indirect
PyPIjmespath1.1.0indirect
PyPImccabe0.7.0indirect
PyPInumpy2.4.6indirect
PyPIpackaging26.2indirect
PyPIpsycopg-c3.3.4indirect
PyPIpycodestyle2.9.1indirect
PyPIpycparser3.0indirect
PyPIpyerfa2.0.1.5indirect
PyPIpyflakes2.5.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytz2026.2indirect
PyPIredis7.4.0indirect
PyPIresponses0.21.0indirect
PyPIs3transfer0.17.0indirect
PyPIsetuptools82.0.1indirect
PyPIsix1.17.0indirect
PyPIsqlparse0.5.5indirect
PyPItyping-extensions4.15.0indirect
PyPItzdata2026.2indirect
PyPIvcs-versioning1.1.1indirect
PyPIvine5.1.0indirect
PyPIzope-event6.2indirect
PyPIzope-interface8.4indirect
Dependency advisories 7

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

PackageVersionRelationSeverityAdvisoriesFixed in
django6.0.5directhigh206.1.1
djangorestframework3.17.1directhigh73.18.2
markdown3.0.1directhigh23.8.1
urllib31.26.20directhigh142.8.0
certifi2026.5.20indirecthigh22026.10.18
sqlparse0.5.5indirecthigh100.6.0
setuptools82.0.1indirectmoderate384.1.0

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.