Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 07:41 UTC

FluidifyAI / Regen

Open-source oncall management Alerts, Incidents, AI post-mortems. Self-hosted alternative to PagerDuty & incident.io. BYO-AI, Works with Prometheus, Grafana, Datadog, Slack, and Teams

Go · TypeScriptCustom license★ 91 stars⑂ 20 forkssince Feb 2026View on GitHub ↗
KindNetwork serviceWeb interfaceCommand-line toolhow this is determined

FluidifyAI/Regen holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (91/100) and lowest on Sustainability & Governance (46/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

FluidifyAIOrganization
6 followers3 public repossince Nov 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/FluidifyAI/Regen/backendv0.15.0-1148 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
18.7/36Commit cadence — 27/52 weeks with commits
18/18Commit volume — 298 commits in the last year
10/10OpenSSF Scorecard: Maintained — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year298
human_commit_share1
days_since_last_push1
active_weeks_last_year27

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 13 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~16.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count13
latest_release_tagv1.2.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases16.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?

65Good · 17% of overall
How it's scored
31.7/60Stars — 91 stars
10.7/25Forks — 20 forks
3.3/15Watchers — 5 watchers
Inputs used
forks20
stars91
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, goreportcard.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

46Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.8/22.5Commit distribution — top contributor authored 88% of commits
5.4/13.5Contributor breadth — 4 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.876
How it's scored
19.4/42Issue resolution — 46% of issues closed
18.9/30PR acceptance — 94/149 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs94
open_issues7
closed_issues6
prs_merged_7d4
prs_decided_7d4
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0.462
closed_unmerged_prs55
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.1/25Owner reach — 6 followers of FluidifyAI
6.3/25Track record — 3 public repos, account ~0 yr old
Inputs used
followers6
owner_typeOrganization
is_verifiedno
owner_loginFluidifyAI
public_repos3
account_age_days348
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 148 days ago
4/20Version history — 1 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/FluidifyAI/Regen/backend
ecosystemsgo
any_deprecatedno
min_days_since_publish148

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.cjs, .golangci.yml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 25 out of 27 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://fluidify.ai
10/10Repository description
10/10Topics — 13 topics
0/10Wiki
Inputs used
topicsalerting, devops, grafana, incident-management, observability, on-call, pagerduty-alternative, prometheus, self-hosted, slack, sre, ai-sre, oncall-schedule
has_wikino
homepagehttps://fluidify.ai
docs_sitehttps://fluidify.ai
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 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
2.2/2.5CI-Tests — 25 out of 27 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 45 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

76Good · 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://fluidify.ai/llms.txt)
40/40Legible commit history — 87 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://fluidify.ai/llms.txt
legible_history_share0.87
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .eslintrc.cjs, .golangci.yml
11/11Static type checking — frontend/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsfrontend/tsconfig.json
agent_commit_share0.02
toolchain_manifestsbackend/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
54.7/55Manageable file sizes — 2/424 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes80,997
source_files_sampled424
oversized_source_files2

Key facts

91GitHub stars
4contributors
298commits, last 12 months
1days since last push
13releases
1bus factor
7open 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 ★ / 20 ⇿
0Stars
20Forks
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.

5810131518202072026-042026-072026-10
Major 1Minor 8Patch 2
OpenSSF Scorecard 5.2 / 10
5.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-20 07:41 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests25 out of 27 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained27 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities45 existing vulnerabilities detected
Direct dependencies 40
RegistryPackageVersion constraintManifest
Gofirebase.google.com/go/v4v4.21.0backend/go.mod
Gogithub.com/SherClockHolmes/webpush-gov1.4.0backend/go.mod
Gogithub.com/alicebob/miniredis/v2v2.36.1backend/go.mod
Gogithub.com/crewjam/samlv0.5.1backend/go.mod
Gogithub.com/gin-gonic/ginv1.10.0backend/go.mod
Gogithub.com/go-playground/validator/v10v10.25.0backend/go.mod
Gogithub.com/golang-jwt/jwt/v5v5.3.1backend/go.mod
Gogithub.com/golang-migrate/migrate/v4v4.19.1backend/go.mod
Gogithub.com/google/uuidv1.6.0backend/go.mod
Gogithub.com/joho/godotenvv1.5.1backend/go.mod
Gogithub.com/prometheus/client_golangv1.23.2backend/go.mod
Gogithub.com/prometheus/client_modelv0.6.2backend/go.mod
Gogithub.com/redis/go-redis/extra/redisotel/v9v9.17.3backend/go.mod
Gogithub.com/redis/go-redis/v9v9.17.3backend/go.mod
Gogithub.com/slack-go/slackv0.17.3backend/go.mod
Gogithub.com/spf13/cobrav1.10.2backend/go.mod
Gogithub.com/stretchr/testifyv1.11.1backend/go.mod
Gogo.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelginv0.60.0backend/go.mod
Gogo.opentelemetry.io/contrib/instrumentation/net/http/otelhttpv0.68.0backend/go.mod
Gogo.opentelemetry.io/otelv1.43.0backend/go.mod
Gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpcv1.43.0backend/go.mod
Gogo.opentelemetry.io/otel/sdkv1.43.0backend/go.mod
Gogo.opentelemetry.io/otel/tracev1.43.0backend/go.mod
Gogolang.org/x/cryptov0.52.0backend/go.mod
Gogolang.org/x/oauth2v0.36.0backend/go.mod
Gogoogle.golang.org/apiv0.279.0backend/go.mod
Gogorm.io/driver/postgresv1.6.0backend/go.mod
Gogorm.io/driver/sqlitev1.6.0backend/go.mod
Gogorm.io/gormv1.31.1backend/go.mod
Gogorm.io/plugin/opentelemetryv0.1.16backend/go.mod
npm@dnd-kit/core^6.3.1frontend/package.json
npm@dnd-kit/sortable^10.0.0frontend/package.json
npm@dnd-kit/utilities^3.2.2frontend/package.json
npmframer-motion^12.35.1frontend/package.json
npmlucide-react^0.563.0frontend/package.json
npmposthog-js^1.391.9frontend/package.json
npmreact^18.2.0frontend/package.json
npmreact-dom^18.2.0frontend/package.json
npmreact-router-dom^6.22.0frontend/package.json
npmweb-vitals^6.2.1frontend/package.json
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 statistics — Go.