Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 11:01 UTC

rootly-io / rootly-go

A golang library for the Rootly API

GoMIT★ 3 stars⑂ 2 forkssince Feb 2021View on GitHub ↗

rootly-io/rootly-go holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Vitality (85/100) and lowest on Community & Adoption (37/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

RootlyOrganization
41 followers70 public repossince Jan 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/rootlyhq/rootly-gopoints to another repo — not scoredv0.11.1-174 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 volume151 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year151
human_commit_share
days_since_last_push1
active_weeks_last_year24
How it's scored
27/27Ships releases18 releases published
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~15.4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count18
latest_release_tagv0.11.1
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases15.4

Community & Adoption

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

37Weak · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks2 forks
3.9/15Watchers6 watchers
Inputs used
forks2
stars3
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
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?

74Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.1/22.5Commit distributiontop contributor authored 33% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 20 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled7
top_contributor_share0.33
How it's scored
36.8/42Issue resolution88% of issues closed
25.6/30PR acceptance112/131 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 7/9 approved changesets -- score normalized to 7
Inputs used
merged_prs112
open_issues1
closed_issues7
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.875
closed_unmerged_prs19
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.7/25Owner reach41 followers of rootlyhq
23.9/25Track record70 public repos, account ~5 yr old
Inputs used
followers41
owner_typeOrganization
is_verified
owner_loginrootlyhq
public_repos70
account_age_days1,994
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://rootly.com
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsapi, client, go, rootly, http
has_wikiyes
homepagehttps://rootly.com
docs_sitehttps://rootly.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 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
2.5/2.5CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 7/9 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 20 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Packaging. 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.

78Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,379
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile, mise.toml
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, mise.toml
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeGo (statically typed)
42.8/55Manageable file sizes2/9 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes8,219,176
source_files_sampled9
oversized_source_files2
How it's scored
40/40API schema (OpenAPI/GraphQL/proto).vendored/rootly-api/swagger.json
0/20MCP servernot applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_files.vendored/rootly-api/swagger.json
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

3GitHub stars
7contributors
151commits, last 12 months
1days since last push
18releases
2bus factor
1open issues
Gopackage ecosystems

Data collection warnings

  • go package 'github.com/rootlyhq/rootly-go' points at a different repository (https://github.com/rootlyhq/rootly-go); excluded from ecosystem scoring
  • Could not fetch go package 'github.com/rootlyhq/rootly-go/tools' from its registry

More detail

OpenSSF Scorecard 5.8 / 10
5.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-07-17 11:00 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 7/9 approved changesets -- score normalized to 7
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Gogithub.com/getkin/kin-openapiv0.140.0go.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/oapi-codegen/nullablev1.2.0go.mod
Gogithub.com/oapi-codegen/runtimev1.4.2go.mod
Gogithub.com/oapi-codegen/oapi-codegen/v2v2.7.1-0.20260622205726-5d02a03ac0e9tools/go.mod
All dependencies 25

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

RegistryPackageVersionRelation
Gogithub.com/getkin/kin-openapiv0.140.0direct
Gogithub.com/google/uuidv1.6.0direct
Gogithub.com/oapi-codegen/nullablev1.2.0direct
Gogithub.com/oapi-codegen/oapi-codegen/v2v2.7.1-0.20260622205726-5d02a03ac0e9direct
Gogithub.com/oapi-codegen/runtimev1.4.2direct
Gogithub.com/apapsch/go-jsonmerge/v2v2.0.0indirect
Gogithub.com/dprotaso/go-yitv0.0.0-20220510233725-9ba8df137936indirect
Gogithub.com/go-openapi/jsonpointerv0.22.5indirect
Gogithub.com/go-openapi/jsonpointerv0.23.1indirect
Gogithub.com/go-openapi/swag/jsonnamev0.25.5indirect
Gogithub.com/go-openapi/swag/jsonnamev0.26.0indirect
Gogithub.com/kr/prettyv0.3.1indirect
Gogithub.com/oasdiff/yamlv0.1.0indirect
Gogithub.com/oasdiff/yaml3v0.0.13indirect
Gogithub.com/santhosh-tekuri/jsonschema/v6v6.0.2indirect
Gogithub.com/speakeasy-api/jsonpathv0.6.3indirect
Gogithub.com/speakeasy-api/openapiv1.23.1indirect
Gogithub.com/vmware-labs/yaml-jsonpathv0.3.2indirect
Gogo.yaml.in/yaml/v3v3.0.4indirect
Gogolang.org/x/modv0.36.0indirect
Gogolang.org/x/syncv0.20.0indirect
Gogolang.org/x/textv0.32.0indirect
Gogolang.org/x/textv0.37.0indirect
Gogolang.org/x/toolsv0.45.0indirect
Gogopkg.in/yaml.v3v3.0.1indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.