Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 04:14 UTC

Wind-River / ccli

GoNo license detected★ 2 stars⑂ 0 forkssince Apr 2023View on GitHub ↗
KindCommand-line toolhow this is determined

Wind-River/ccli holds a health index of 24 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (56/100) and lowest on Community & Adoption (13/100). It was last updated 429 days ago. A single contributor accounts for most of its recent work.

24
overall / 100
At Risk

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.

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

Ownership

Wind RiverOrganization
154 followers96 public repossince Oct 2015

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?

22At Risk · 21% of overall
How it's scored
0/36Push recencylast push 429 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push429
active_weeks_last_year0
How it's scored
27/27Ships releases15 releases published
7.2/36Release recencylatest release 429 days ago
19.8/27Release cadencea release every ~89.4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count15
latest_release_tagv1.2.0
releases_from_tagsno
days_since_latest_release429
mean_days_between_releases89.4

Community & Adoption

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

13Critical · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
1.7/15Watchers3 watchers
Inputs used
forks0
stars2
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.2/22.5Commit distributiontop contributor authored 77% of commits
5.4/13.5Contributor breadth4 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.768
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance9/9 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 5/11 approved changesets -- score normalized to 4
Inputs used
merged_prs9
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15.7/25Owner reach154 followers of Wind-River
25/25Track record96 public repos, account ~10 yr old
Inputs used
followers154
owner_typeOrganization
is_verifiedno
owner_loginWind-River
public_repos96
account_age_days3,991

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

32At Risk · 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 9 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
3/7.5Code-ReviewFound 5/11 approved changesets -- score normalized to 4
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
0/7.5Vulnerabilities24 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate1.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories32
affected_packages10
assessed_packages69
unassessed_packages0
affected_by_severityhigh 4, moderate 1, unknown 5
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 69 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.2/40Legible commit history10 of 65 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.154
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapgo.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 65
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/22 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes15,654
source_files_sampled22
oversized_source_files0

Key facts

2GitHub stars
4contributors
0commits, last 12 months
429days since last push
15releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 1.5 / 10
1.5aggregate

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-20 04:13 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 5/11 approved changesets -- score normalized to 4
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
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.
n/aToken-PermissionsNo tokens found
0Vulnerabilities24 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Gobitbucket.wrs.com/scm/weststar/graphql-upload-go.gitv1.0.0-rc.0go.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/hasura/go-graphql-clientv0.9.2go.mod
Gogithub.com/pkg/errorsv0.9.1go.mod
Gogithub.com/spf13/cobrav1.8.0go.mod
Gogithub.com/spf13/viperv1.18.2go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
Gobitbucket.wrs.com/scm/weststar/communication-bus.gitv0.5.1go.mod
Gobitbucket.wrs.com/scm/weststar/pulsar-schemas-go.gitv0.6.0go.mod
All dependencies 69

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

RegistryPackageVersionRelation
Gobitbucket.wrs.com/scm/weststar/communication-bus.git0.5.1direct
Gobitbucket.wrs.com/scm/weststar/graphql-upload-go.git1.0.0-rc.0direct
Gobitbucket.wrs.com/scm/weststar/pulsar-schemas-go.git0.6.0direct
Gogithub.com/google/uuid1.6.0direct
Gogithub.com/hasura/go-graphql-client0.9.2direct
Gogithub.com/pkg/errors0.9.1direct
Gogithub.com/spf13/cobra1.8.0direct
Gogithub.com/spf13/viper1.18.2direct
Gogopkg.in/yaml.v33.0.1direct
Gogithub.com/99designs/go-keychain0.0.0-20191008050251-8e49817e8af4indirect
Gogithub.com/99designs/keyring1.2.1indirect
Gogithub.com/apache/pulsar-client-go0.14.0indirect
Gogithub.com/ardielle/ardielle-go1.5.2indirect
Gogithub.com/athenz/athenz1.10.39indirect
Gogithub.com/beorn7/perks1.0.1indirect
Gogithub.com/bits-and-blooms/bitset1.4.0indirect
Gogithub.com/cespare/xxhash/v22.2.0indirect
Gogithub.com/danieljoos/wincred1.1.2indirect
Gogithub.com/datadog/zstd1.5.0indirect
Gogithub.com/dvsekhvalnov/jose2go1.6.0indirect
Gogithub.com/fsnotify/fsnotify1.7.0indirect
Gogithub.com/godbus/dbus0.0.0-20190726142602-4481cbc300e2indirect
Gogithub.com/golang-jwt/jwt3.2.1+incompatibleindirect
Gogithub.com/golang-jwt/jwt/v55.2.1indirect
Gogithub.com/golang/protobuf1.5.4indirect
Gogithub.com/golang/snappy0.0.4indirect
Gogithub.com/gsterjov/go-libsecret0.0.0-20161001094733-a6f4afe4910cindirect
Gogithub.com/hamba/avro/v22.22.2-0.20240625062549-66aad10411d9indirect
Gogithub.com/hashicorp/errwrap1.1.0indirect
Gogithub.com/hashicorp/go-multierror1.1.1indirect
Gogithub.com/hashicorp/hcl1.0.0indirect
Gogithub.com/inconshreveable/mousetrap1.1.0indirect
Gogithub.com/json-iterator/go1.1.12indirect
Gogithub.com/klauspost/compress1.17.9indirect
Gogithub.com/linkedin/goavro/v22.9.8indirect
Gogithub.com/magiconair/properties1.8.7indirect
Gogithub.com/matttproud/golang_protobuf_extensions1.0.4indirect
Gogithub.com/mitchellh/mapstructure1.5.0indirect
Gogithub.com/modern-go/concurrent0.0.0-20180306012644-bacd9c7ef1ddindirect
Gogithub.com/modern-go/reflect21.0.2indirect
Gogithub.com/mtibben/percent0.2.1indirect
Gogithub.com/pelletier/go-toml/v22.1.0indirect
Gogithub.com/pierrec/lz42.0.5+incompatibleindirect
Gogithub.com/prometheus/client_golang1.14.0indirect
Gogithub.com/prometheus/client_model0.3.0indirect
Gogithub.com/prometheus/common0.37.0indirect
Gogithub.com/prometheus/procfs0.8.0indirect
Gogithub.com/sagikazarmark/locafero0.4.0indirect
Gogithub.com/sagikazarmark/slog-shim0.1.0indirect
Gogithub.com/sirupsen/logrus1.9.3indirect
Gogithub.com/sourcegraph/conc0.3.0indirect
Gogithub.com/spaolacci/murmur31.1.0indirect
Gogithub.com/spf13/afero1.11.0indirect
Gogithub.com/spf13/cast1.6.0indirect
Gogithub.com/spf13/pflag1.0.5indirect
Gogithub.com/subosito/gotenv1.6.0indirect
Gogo.uber.org/atomic1.9.0indirect
Gogo.uber.org/multierr1.9.0indirect
Gogolang.org/x/exp0.0.0-20230905200255-921286631fa9indirect
Gogolang.org/x/mod0.18.0indirect
Gogolang.org/x/net0.23.0indirect
Gogolang.org/x/oauth20.15.0indirect
Gogolang.org/x/sys0.19.0indirect
Gogolang.org/x/term0.19.0indirect
Gogolang.org/x/text0.14.0indirect
Gogoogle.golang.org/appengine1.6.7indirect
Gogoogle.golang.org/protobuf1.34.1indirect
Gogopkg.in/ini.v11.67.0indirect
Gonhooyr.io/websocket1.8.7indirect
Dependency advisories 10

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

PackageVersionRelationSeverityAdvisoriesFixed in
github.com/dvsekhvalnov/jose2go1.6.0indirecthigh21.7.0
github.com/golang-jwt/jwt3.2.1+incompatibleindirecthigh25.2.2
github.com/golang-jwt/jwt/v55.2.1indirecthigh25.2.2
golang.org/x/oauth20.15.0indirecthigh20.27.0
golang.org/x/net0.23.0indirectmoderate161.27.0-rc.3
github.com/hamba/avro/v22.22.2-0.20240625062549-66aad10411d9indirectunknown32.33.0
github.com/klauspost/compress1.17.9indirectunknown11.18.7
golang.org/x/mod0.18.0indirectunknown21.27.0-rc.3
golang.org/x/sys0.19.0indirectunknown10.44.0
golang.org/x/text0.14.0indirectunknown10.39.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.