Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 02:34 UTC

roman-mazur / cuetf

CUE schemas for Terraform

CUEMIT★ 9 stars⑂ 0 forkssince Oct 2022View on GitHub ↗

roman-mazur/cuetf holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (92/100) and lowest on Community & Adoption (31/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Roman MazurPersonal account
137 followers83 public repossince Jun 2010Ubisoft

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gormazur.io/cuetfv0.2607.3-254 days ago

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
30.5/36Commit cadence44/52 weeks with commits
18/18Commit volume710 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year710
human_commit_share
days_since_last_push4
active_weeks_last_year44
How it's scored
16.2/27Ships releases25 version tags (no GitHub releases)
36/36Release recencylatest release 4 days ago
27/27Release cadencea release every ~10.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count25
latest_release_tagv0.2607.3
releases_from_tagsyes
days_since_latest_release4
mean_days_between_releases10.8
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?

31At Risk · 17% of overall
How it's scored
14.6/60Stars9 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars9
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6/22.5Commit distributiontop contributor authored 73% of commits
4.1/13.5Contributor breadth3 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.734
How it's scored
42/42Issue resolution100% of issues closed
28.8/30PR acceptance171/178 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/5 approved changesets -- score normalized to 0
Inputs used
merged_prs171
open_issues0
closed_issues1
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs7
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.4/25Owner reach137 followers of roman-mazur
25/25Track record83 public repos, account ~16 yr old
Inputs used
followers137
owner_typeUser
is_verified
owner_loginroman-mazur
public_repos83
account_age_days5,873
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 4 days ago
20/20Version history25 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrmazur.io/cuetf
ecosystemsgo
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests9 out of 9 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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicscue, iac, opentofu, 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?

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests9 out of 9 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
0/7.5Code-ReviewFound 0/5 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
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 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging, 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.

62Moderate · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.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_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes4,012
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeCUE without a type-check config
55/55Manageable file sizes0/50 source files over 60KB
Inputs used
primary_languageCUE
largest_source_bytes9,128
source_files_sampled50
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
40/40Runnable examplesexamples, sample
Inputs used
example_dirsexamples, sample
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

9GitHub stars
3contributors
710commits, last 12 months
4days since last push
25releases
1bus factor
0open issues
Gopackage ecosystems

More detail

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-07-17 02:34 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/5 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
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Gocuelang.org/gov0.17.0go.mod
Gogithub.com/hashicorp/hcl/v2v2.24.0go.mod
Gogithub.com/rogpeppe/go-internalv1.15.0go.mod
All dependencies 30

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

RegistryPackageVersionRelation
Gocuelang.org/gov0.17.0direct
Gogithub.com/hashicorp/hcl/v2v2.24.0direct
Gogithub.com/rogpeppe/go-internalv1.15.0direct
Gocuelabs.dev/go/oci/ociregistryv0.0.0-20260601085548-328ff8e2c943indirect
Gogithub.com/agext/levenshteinv1.2.3indirect
Gogithub.com/apparentlymart/go-textseg/v15v15.0.0indirect
Gogithub.com/cockroachdb/apd/v3v3.2.3indirect
Gogithub.com/coder/websocketv1.8.14indirect
Gogithub.com/emicklei/protov1.14.3indirect
Gogithub.com/google/go-cmpv0.7.0indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/inconshreveable/mousetrapv1.1.0indirect
Gogithub.com/mitchellh/go-wordwrapv1.0.1indirect
Gogithub.com/opencontainers/go-digestv1.0.0indirect
Gogithub.com/opencontainers/image-specv1.1.1indirect
Gogithub.com/pelletier/go-toml/v2v2.3.1indirect
Gogithub.com/protocolbuffers/txtpbfmtv0.0.0-20260420112717-c39628bde8b5indirect
Gogithub.com/spf13/cobrav1.10.2indirect
Gogithub.com/spf13/pflagv1.0.10indirect
Gogithub.com/tetratelabs/wazerov1.12.0indirect
Gogithub.com/zclconf/go-ctyv1.17.0indirect
Gogo.yaml.in/yaml/v3v3.0.4indirect
Gogolang.org/x/modv0.37.0indirect
Gogolang.org/x/netv0.56.0indirect
Gogolang.org/x/oauth2v0.36.0indirect
Gogolang.org/x/syncv0.21.0indirect
Gogolang.org/x/sysv0.46.0indirect
Gogolang.org/x/textv0.38.0indirect
Gogolang.org/x/toolsv0.45.0indirect
Gogoogle.golang.org/protobufv1.33.0indirect
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.