Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 01:54 UTC

spacelift-io / spacelift-migration-kit

Migrate from your current solution to Spacelift with minimal friction

PythonMIT★ 41 stars⑂ 7 forkssince Sep 2022View on GitHub ↗
KindCommand-line toolhow this is determined

spacelift-io/spacelift-migration-kit holds a health index of 51 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (72/100) and lowest on Vitality (35/100). It was last updated 102 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SpaceliftOrganization · verified domain
272 followers135 public repossince Jul 2019

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?

35Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 102 days ago
4.2/36Commit cadence — 6/52 weeks with commits
10.3/18Commit volume — 13 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year13
human_commit_share0.87
days_since_last_push102
active_weeks_last_year6
How it's scored
27/27Ships releases — 6 releases published
0/36Release recency — latest release 923 days ago
19.8/27Release cadence — a release every ~89.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count6
latest_release_tagv2.0.0-alpha1
releases_from_tagsno
days_since_latest_release923
mean_days_between_releases89.4
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
26/60Stars — 41 stars
6.5/25Forks — 7 forks
5.8/15Watchers — 12 watchers
Inputs used
forks7
stars41
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/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_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.3/22.5Commit distribution — top contributor authored 72% of commits
12.2/13.5Contributor breadth — 9 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.718
How it's scored
16.8/42Issue resolution — 40% of issues closed
20.4/30PR acceptance — 68/100 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 10/20 approved changesets -- score normalized to 5
Inputs used
merged_prs68
open_issues6
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.4
closed_unmerged_prs32
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
20/20Verified domain
17.5/25Owner reach — 272 followers of spacelift-io
25/25Track record — 135 public repos, account ~7 yr old
Inputs used
followers272
owner_typeOrganization
is_verifiedyes
owner_loginspacelift-io
public_repos135
account_age_days2,642

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.black])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 6 out of 16 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsiac, spacelift, terraform
has_wikino
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?

43Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.8/2.5CI-Tests — 6 out of 16 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 10/20 approved changesets -- score normalized to 5
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
2/5SAST — SAST tool is not run on all commits -- score normalized to 4
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 — 27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
8/35Direct dependencies free of known advisories — 3 affected: jinja2 3.1.4 (high 8.8), python-dotenv 1.0.1 (moderate 6.6), requests 2.32.2 (moderate 5.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
26.3/40No advisories left outstanding — 3 advisory-carrying package(s) unaddressed past 90 days; oldest published 664 days ago
Inputs used
sourceosv
advisories53
affected_packages11
assessed_packages66
unassessed_packages0
affected_by_severitycritical 1, high 4, moderate 5, low 1
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 66 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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.spacelift.io/llms.txt)
40/40Legible commit history — 68 of 87 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.spacelift.io/llms.txt
legible_history_share0.782
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — noxfile.py
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.black])
0/11Static type checking
10/10Reproducible environment — devcontainer, Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 13 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileyes
typed_languageno
bootstrap_filesnoxfile.py
has_devcontaineryes
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.13
How it's scored
0/45Type-checkable code — Python without a type-check config
52.2/55Manageable file sizes — 1/20 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes80,072
source_files_sampled20
oversized_source_files1

Key facts

41GitHub stars
9contributors
13commits, last 12 months
102days since last push
6releases
1bus factor
6open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 7 ⇿
0Stars
7Forks
2Releases

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.

1234567722023-072024-122026-04
Major 1Minor 0Patch 0

Each point covers 3 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-19 01:53 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
3CI-Tests6 out of 16 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 10/20 approved changesets -- score normalized to 5
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4SASTSAST tool is not run on all commits -- score normalized to 4
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
PyPIclick8.1.7pyproject.toml
PyPIclick-help-colors^0.9.4pyproject.toml
PyPIclickloader0.2.0pyproject.toml
PyPIenvyaml1.10.211231pyproject.toml
PyPIicecream2.1.3pyproject.toml
PyPIjinja23.1.4pyproject.toml
PyPIpydash8.0.1pyproject.toml
PyPIpython-benedict0.33.2pyproject.toml
PyPIpython-dotenv1.0.1pyproject.toml
PyPIpython-git-info^0.8.3pyproject.toml
PyPIpython-on-whales0.71.0pyproject.toml
PyPIpython-slugify8.0.4pyproject.toml
PyPIpyyaml6.0.1pyproject.toml
PyPIrequests2.32.2pyproject.toml
PyPIrequests-toolbelt1.0.0pyproject.toml
PyPIrich13.7.1pyproject.toml
PyPIsemver^3.0.2pyproject.toml
PyPIxlsxwriter3.2.0pyproject.toml
PyPIpydantic^2.10.6pyproject.toml
All dependencies 66

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

RegistryPackageVersionRelation
PyPIclick8.1.7direct
PyPIclick-help-colors0.9.4direct
PyPIclickloader0.2.0direct
PyPIenvyaml1.10.211231direct
PyPIicecream2.1.3direct
PyPIjinja23.1.4direct
PyPIpydantic2.10.6direct
PyPIpydash8.0.1direct
PyPIpython-benedict0.33.2direct
PyPIpython-dotenv1.0.1direct
PyPIpython-git-info0.8.3direct
PyPIpython-on-whales0.71.0direct
PyPIpython-slugify8.0.4direct
PyPIpyyaml6.0.1direct
PyPIrequests2.32.2direct
PyPIrequests-toolbelt1.0.0direct
PyPIrich13.7.1direct
PyPIsemver3.0.2direct
PyPIxlsxwriter3.2.0direct
PyPIannotated-types0.6.0indirect
PyPIargcomplete3.3.0indirect
PyPIasttokens2.4.1indirect
PyPIcertifi2024.2.2indirect
PyPIcharset-normalizer3.3.2indirect
PyPIcolorama0.4.6indirect
PyPIcolorlog6.8.2indirect
PyPIcoverage7.5.1indirect
PyPIdistlib0.3.8indirect
PyPIexceptiongroup1.2.1indirect
PyPIexecuting2.0.1indirect
PyPIfilelock3.13.4indirect
PyPIidna3.7indirect
PyPIiniconfig2.0.0indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkupsafe2.1.5indirect
PyPImdurl0.1.2indirect
PyPImultidict6.0.5indirect
PyPImypy1.10.0indirect
PyPImypy-extensions1.0.0indirect
PyPInox2024.4.15indirect
PyPInox-poetry1.0.3indirect
PyPIpackaging24.0indirect
PyPIplatformdirs4.2.0indirect
PyPIpluggy1.5.0indirect
PyPIpydantic-core2.27.2indirect
PyPIpygments2.17.2indirect
PyPIpytest8.2.1indirect
PyPIpytest-cov5.0.0indirect
PyPIpytest-dotenv0.5.2indirect
PyPIpytest-mock3.14.0indirect
PyPIpytest-recording0.13.1indirect
PyPIpython-fsutil0.14.1indirect
PyPIruff0.4.4indirect
PyPIshellingham1.5.4indirect
PyPIsix1.16.0indirect
PyPItext-unidecode1.3indirect
PyPItomli2.0.1indirect
PyPItomlkit0.12.4indirect
PyPItqdm4.66.3indirect
PyPItyper0.12.3indirect
PyPItyping-extensions4.12.2indirect
PyPIurllib31.26.18indirect
PyPIvcrpy6.0.1indirect
PyPIvirtualenv20.25.3indirect
PyPIwrapt1.16.0indirect
PyPIyarl1.9.4indirect
Dependency advisories 11

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

PackageVersionRelationSeverityAdvisoriesFixed in
virtualenv20.25.3indirectcritical1221.7.13
jinja23.1.4directhigh63.1.6
certifi2024.2.2indirecthigh22024.7.4
urllib31.26.18indirecthigh162.8.0
vcrpy6.0.1indirecthigh18.2.1
python-dotenv1.0.1directmoderate21.2.2
requests2.32.2directmoderate42.33.0
filelock3.13.4indirectmoderate43.20.3
idna3.7indirectmoderate23.15
pytest8.2.1indirectmoderate29.0.3
pygments2.17.2indirectlow22.20.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.