Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 15:15 UTC

zeitlos / lucity

Lucity is an open-source Vercel/Railway/Heroku alternative deliberately designed to avoid lock-in. Push to deploy, one-click PostgreSQL, Redis and S3 object storage.

Go · Vue · TypeScriptAGPL-3.0★ 39 stars⑂ 6 forkssince Feb 2026View on GitHub ↗
KindNetwork serviceLibraryhow this is determined

zeitlos/lucity holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (85/100) and lowest on Security (36/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

zeitlosOrganization
6 followers15 public repossince May 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/zeitlos/lucityv26.7.2+incompatible-1554 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
16.6/36Commit cadence24/52 weeks with commits
18/18Commit volume869 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year869
human_commit_share1
days_since_last_push1
active_weeks_last_year24
How it's scored
27/27Ships releases11 releases published
36/36Release recencylatest release 47 days ago
27/27Release cadencea release every ~5 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count11
latest_release_tagv26.7.3-rc.1
releases_from_tagsno
days_since_latest_release47
mean_days_between_releases5

Community & Adoption

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

54Moderate · 17% of overall
How it's scored
25.6/60Stars39 stars
5.8/25Forks6 forks
1.7/15Watchers3 watchers
Inputs used
forks6
stars39
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (AGPL-3.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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
31.1/42Issue resolution74% of issues closed
30/30PR acceptance39/39 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs39
open_issues13
closed_issues37
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.74
closed_unmerged_prs0
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 backingorganization-owned
0/20Verified domain
6.1/25Owner reach6 followers of zeitlos
19.5/25Track record15 public repos, account ~5 yr old
Inputs used
followers6
owner_typeOrganization
is_verifiedno
owner_loginzeitlos
public_repos15
account_age_days1,958

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 54 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/zeitlos/lucity
ecosystemsgo
any_deprecatedno
min_days_since_publish54

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://lucity.cloud
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsdeployment, helm, kubernetes, cloud, self-hosted
has_wikino
homepagehttps://lucity.cloud
docs_sitehttps://lucity.cloud
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities67 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate3.6

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.

74Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, services/dashboard/CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://lucity.cloud/llms.txt)
9.6/40Legible commit history18 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://lucity.cloud/llms.txt
legible_history_share0.18
agent_instruction_filesCLAUDE.md, services/dashboard/CLAUDE.md
agent_instruction_max_bytes5,922
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config
11/11Static type checkingservices/dashboard/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsservices/dashboard/tsconfig.json
agent_commit_share0
toolchain_manifestscharts/go.mod, cli/go.mod, pkg/go.mod, services/builder/go.mod, services/cashier/go.mod, services/conductor/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
54.1/55Manageable file sizes5/323 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes1,131,941
source_files_sampled323
oversized_source_files5
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)pkg/cashier/cashier.proto, pkg/conductor/conductor.proto, services/conductor/internal/api/graphql/schema/apitoken.graphqls, services/conductor/internal/api/graphql/schema/auth.graphqls, services/conductor/internal/api/graphql/schema/backup.graphqls, services/conductor/internal/api/graphql/schema/billing.graphqls, services/conductor/internal/api/graphql/schema/database.graphqls, services/conductor/internal/api/graphql/schema/eject.graphqls, services/conductor/internal/api/graphql/schema/environment.graphqls, services/conductor/internal/api/graphql/schema/github.graphqls, services/conductor/internal/api/graphql/schema/keyvaluestore.graphqls, services/conductor/internal/api/graphql/schema/logs.graphqls, services/conductor/internal/api/graphql/schema/metrics.graphqls, services/conductor/internal/api/graphql/schema/objectstorage.graphqls, services/conductor/internal/api/graphql/schema/project.graphqls, services/conductor/internal/api/graphql/schema/registry.graphqls, services/conductor/internal/api/graphql/schema/release.graphqls, services/conductor/internal/api/graphql/schema/scan.graphqls, services/conductor/internal/api/graphql/schema/schema.graphqls, services/conductor/internal/api/graphql/schema/service.graphqls, services/conductor/internal/api/graphql/schema/variable.graphqls, services/conductor/internal/api/graphql/schema/volume.graphqls, services/conductor/internal/api/graphql/schema/vulnerability.graphqls, services/conductor/internal/api/graphql/schema/workspace.graphqls
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_filespkg/cashier/cashier.proto, pkg/conductor/conductor.proto, services/conductor/internal/api/graphql/schema/apitoken.graphqls, services/conductor/internal/api/graphql/schema/auth.graphqls, services/conductor/internal/api/graphql/schema/backup.graphqls, services/conductor/internal/api/graphql/schema/billing.graphqls, services/conductor/internal/api/graphql/schema/database.graphqls, services/conductor/internal/api/graphql/schema/eject.graphqls, services/conductor/internal/api/graphql/schema/environment.graphqls, services/conductor/internal/api/graphql/schema/github.graphqls, services/conductor/internal/api/graphql/schema/keyvaluestore.graphqls, services/conductor/internal/api/graphql/schema/logs.graphqls, services/conductor/internal/api/graphql/schema/metrics.graphqls, services/conductor/internal/api/graphql/schema/objectstorage.graphqls, services/conductor/internal/api/graphql/schema/project.graphqls, services/conductor/internal/api/graphql/schema/registry.graphqls, services/conductor/internal/api/graphql/schema/release.graphqls, services/conductor/internal/api/graphql/schema/scan.graphqls, services/conductor/internal/api/graphql/schema/schema.graphqls, services/conductor/internal/api/graphql/schema/service.graphqls, services/conductor/internal/api/graphql/schema/variable.graphqls, services/conductor/internal/api/graphql/schema/volume.graphqls, services/conductor/internal/api/graphql/schema/vulnerability.graphqls, services/conductor/internal/api/graphql/schema/workspace.graphqls
interfaces_expected_ofnetwork-service

Key facts

39GitHub stars
1contributors
869commits, last 12 months
1days since last push
11releases
1bus factor
13open issues
Go, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
11Releases

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.

123456622026-032026-062026-09
Major 0Minor 0Patch 5
OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-09-19 15:15 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 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
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities67 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Gogithub.com/coder/websocketv1.8.15cli/go.mod
Gogithub.com/modelcontextprotocol/go-sdkv1.6.1cli/go.mod
Gogithub.com/zeitlos/lucity/pkgv0.0.0-20260706084318-3ef7184f18d8cli/go.mod
Gogithub.com/bradleyfalzon/ghinstallation/v2v2.19.0pkg/go.mod
Gogithub.com/coreos/go-oidc/v3v3.19.0pkg/go.mod
Gogithub.com/golang-jwt/jwt/v5v5.3.1pkg/go.mod
Gogithub.com/google/go-github/v68v68.0.0pkg/go.mod
Gogithub.com/lmittmann/tintv1.1.3pkg/go.mod
Gogolang.org/x/oauth2v0.36.0pkg/go.mod
Gogoogle.golang.org/grpcv1.82.0pkg/go.mod
Gogoogle.golang.org/protobufv1.36.12-0.20260120151049-f2248ac996afpkg/go.mod
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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