Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 04:10 UTC

cloudfoundry / syslog-release

BOSH release for forwarding logs (either sent to syslog or picked up /var/vcap/sys/log/**/*)

Go · HTML · ShellApache-2.0★ 14 stars⑂ 58 forkssince Apr 2016View on GitHub ↗

cloudfoundry/syslog-release holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Vitality (92/100) and lowest on Engineering Quality (30/100). It was last updated 4 days ago. 5 contributors account for most of its recent work.

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

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

Ownership

Cloud FoundryOrganization
759 followers573 public repossince Feb 2011

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?

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
30.5/36Commit cadence — 44/52 weeks with commits
18/18Commit volume — 133 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year133
human_commit_share0.85
days_since_last_push4
active_weeks_last_year44
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 10 days ago
27/27Release cadence — a release every ~13.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv12.3.32
releases_from_tagsno
days_since_latest_release10
mean_days_between_releases13.8

Community & Adoption

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

58Moderate · 17% of overall
How it's scored
18.1/60Stars — 14 stars
14.6/25Forks — 58 forks
8.9/15Watchers — 41 watchers
Inputs used
forks58
stars14
watchers41
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

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

79Good · 23% of overall
How it's scored
45.9/54Bus factor — 5 contributor(s) cover half of all commits
15.6/22.5Commit distribution — top contributor authored 31% of commits
13.5/13.5Contributor breadth — 50 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled50
top_contributor_share0.306
How it's scored
39.5/42Issue resolution — 94% of issues closed
24.1/30PR acceptance — 170/212 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/23 approved changesets -- score normalized to 1
Inputs used
merged_prs170
open_issues3
closed_issues47
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.94
closed_unmerged_prs42
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 backing — organization-owned
0/20Verified domain
20.7/25Owner reach — 759 followers of cloudfoundry
25/25Track record — 573 public repos, account ~15 yr old
Inputs used
followers759
owner_typeOrganization
is_verifiedno
owner_logincloudfoundry
public_repos573
account_age_days5,723

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 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-Tests — 0 out of 10 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
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
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?

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/23 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 13 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories18
affected_packages5
assessed_packages35
unassessed_packages2
affected_by_severityhigh 1, moderate 1, unknown 3
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 35 resolved dependencies against OSV. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

60Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
5/40Legible commit history — 8 of 85 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.094
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — tests/go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 15 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no 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_manifeststests/go.mod
dependency_bot_commit_share0.15
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/4 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes11,931
source_files_sampled4
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

14GitHub stars
50contributors
133commits, last 12 months
4days since last push
100releases
5bus factor
3open issues
Go, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 58 ⇿
0Stars
58Forks
93Releases

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.

01020304050605122016-042021-052026-07
Major 1Minor 11Patch 77

Each point covers 10 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-19 04:10 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 10 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/23 approved changesets -- score normalized to 1
10Contributorsproject has 13 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate 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
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
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.
n/aToken-PermissionsNo tokens found
1Vulnerabilities9 existing vulnerabilities detected
All dependencies 37

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

RegistryPackageVersionRelation
Gocode.cloudfoundry.org/go-loggregator/v10v10.3.1indirect
Gogithub.com/cloudfoundry/blackbox0.0.0-20190604033514-9038052aa615indirect
Gogithub.com/go-logr/logrv1.4.3indirect
Gogithub.com/go-task/slim-sprig/v3v3.0.0indirect
Gogithub.com/google/go-cmpv0.7.0indirect
Gogithub.com/google/pprofv0.0.0-20260402051712-545e8a4df936indirect
Gogithub.com/hpcloud/tail1.0.0indirect
Gogithub.com/jtarchie/syslog0.0.0-20190709005936-5fab01d378a6indirect
Gogithub.com/jtarchie/syslog0.0.0-20200616043123-c6861be235b9indirect
Gogithub.com/kr/pretty0.1.0indirect
Gogithub.com/masterminds/semver/v3v3.4.0indirect
Gogithub.com/nu7hatch/gouuid0.0.0-20131221200532-179d4d0c4d8dindirect
Gogithub.com/onsi/ginkgo1.10.1indirect
Gogithub.com/onsi/ginkgo1.16.2indirect
Gogithub.com/onsi/ginkgo/v2v2.33.1indirect
Gogithub.com/onsi/gomega1.12.0indirect
Gogithub.com/onsi/gomega1.5.0indirect
Gogithub.com/onsi/gomegav1.44.0indirect
Gogithub.com/papertrail/remote_syslog20.0.0-20190614180052-09062fc2b02aindirect
Gogithub.com/stretchr/testify1.3.0indirect
Gogithub.com/tedsuo/ifrit0.0.0-20180802180643-bea94bb476ccindirect
Gogithub.com/ziutek/syslog0.0.0-20180426113420-8a9fdf1a8529indirect
Gogo.yaml.in/yaml/v3v3.0.5indirect
Gogolang.org/x/modv0.36.0indirect
Gogolang.org/x/netv0.56.0indirect
Gogolang.org/x/syncv0.21.0indirect
Gogolang.org/x/sys0.0.0-20210525143221-35b2ab0089eaindirect
Gogolang.org/x/sysv0.46.0indirect
Gogolang.org/x/textv0.38.0indirect
Gogolang.org/x/tools0.1.1indirect
Gogolang.org/x/toolsv0.45.0indirect
Gogopkg.in/check.v11.0.0-20180628173108-788fd7840127indirect
Gogopkg.in/fsnotify.v11.4.7indirect
Gogopkg.in/tomb.v11.0.0-20141024135613-dd632973f1e7indirect
Gogopkg.in/yaml.v22.2.2indirect
RubyGemsbosh-template—indirect
RubyGemsrspec—indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 35 packages, which also include development and test pins that never ship: 5 carry known advisories, of which 0 are direct. 2 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
gopkg.in/yaml.v22.2.2indirecthigh62.2.8
golang.org/x/sys0.0.0-20210525143221-35b2ab0089eaindirectmoderate31.18.2
golang.org/x/modv0.36.0indirectunknown21.27.0-rc.3
golang.org/x/netv0.56.0indirectunknown51.27.2
golang.org/x/textv0.38.0indirectunknown20.41.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.