Public recordExcellent
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 22:52 UTC
byteness / keyring
Go library providing a uniform interface across a range of secure credential stores
byteness/keyring holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (48/100). It was last updated 3 days ago. 3 contributors account for most of its recent work.
84
overall / 100Software 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.
84
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)
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 71 is calibrated to 84 on the published index scale (record calibration 2026-08-02).
Ownership
ByteNessOrganization
9 followers5 public repossince May 2025
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| Go | github.com/byteness/keyring | v1.12.0 | - | 55 | 3 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
93
Development activity
89Excellent
How it's scored
| 36/36 | Push recency — last push 3 days ago |
| 24.9/36 | Commit cadence — 36/52 weeks with commits |
| 18/18 | Commit volume — 238 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 238 |
| human_commit_share | — |
| days_since_last_push | 3 |
| active_weeks_last_year | 36 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 44 releases published |
| 36/36 | Release recency — latest release 3 days ago |
| 27/27 | Release cadence — a release every ~10.4 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 44 |
| latest_release_tag | v1.12.0 |
| releases_from_tags | no |
| days_since_latest_release | 3 |
| mean_days_between_releases | 10.4 |
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?
48
Popularity & adoption
29At Risk
How it's scored
| 20.4/60 | Stars — 19 stars |
| 8.3/25 | Forks — 11 forks |
| 0/15 | Watchers — 1 watchers |
Inputs used
| forks | 11 |
| stars | 19 |
| watchers | 1 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
70Good
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
79
How it's scored
| 36/54 | Bus factor — 3 contributor(s) cover half of all commits |
| 16.8/22.5 | Commit distribution — top contributor authored 25% of commits |
| 13.5/13.5 | Contributor breadth — 44 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 21 contributing companies or organizations |
Inputs used
| bus_factor | 3 |
| contributors_sampled | 44 |
| top_contributor_share | 0.254 |
Issue & PR responsiveness
88Excellent
How it's scored
| 42/42 | Issue resolution — 100% of issues closed |
| 27.2/30 | PR acceptance — 86/95 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 7.5/15 | OpenSSF Scorecard: Code-Review — Found 1/2 approved changesets -- score normalized to 5 |
Inputs used
| merged_prs | 86 |
| open_issues | 0 |
| closed_issues | 5 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 1 |
| closed_unmerged_prs | 9 |
| 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.
Ownership & stewardship
56Moderate
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 7.2/25 | Owner reach — 9 followers of ByteNess |
| 8/25 | Track record — 5 public repos, account ~1 yr old |
Inputs used
| followers | 9 |
| owner_type | Organization |
| is_verified | — |
| owner_login | ByteNess |
| public_repos | 5 |
| account_age_days | 423 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on go |
| 35/35 | Publish recency — latest publish 3 days ago |
| 20/20 | Version history — 55 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/byteness/keyring |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 3 |
Engineering Quality
Are baseline engineering and documentation practices in place?
74
Engineering practices
84Excellent
How it's scored
| 24/24 | CI workflows — 4 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .golangci.yaml |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
60Moderate
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 3 topics |
| 10/10 | Wiki |
Inputs used
| topics | credentials, keyring, keystore |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
59
Security posture
59Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 3/7.5 | Branch-Protection — branch protection is not maximal on development and all release branches |
| 2.5/2.5 | CI-Tests — 6 out of 6 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 3.8/7.5 | Code-Review — Found 1/2 approved changesets -- score normalized to 5 |
| 2.5/2.5 | Contributors — project has 21 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 5.9 |
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.
49
Agent context & guidance
1Critical
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .golangci.yaml |
| 11/11 | Static type checking — Go (statically typed) |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no data |
| 5/8 | Automated maintenance — dependency automation configured, none observed in the sampled commits |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | go.sum |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — Go (statically typed) |
| 55/55 | Manageable file sizes — 0/70 source files over 60KB |
Inputs used
| primary_language | Go |
| largest_source_bytes | 27,094 |
| source_files_sampled | 70 |
| oversized_source_files | 0 |
Key facts
19GitHub stars
44contributors
238commits, last 12 months
3days since last push
44releases
3bus factor
0open issues
Gopackage ecosystems
More detail
OpenSSF Scorecard 5.9 / 10
5.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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 4 | Branch-Protection | branch protection is not maximal on development and all release branches |
| 10 | CI-Tests | 6 out of 6 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 5 | Code-Review | Found 1/2 approved changesets -- score normalized to 5 |
| 10 | Contributors | project has 21 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 13
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | github.com/1Password/connect-sdk-go | v1.5.4-0.20250417152128-c154b387248b | go.mod |
| Go | github.com/1password/onepassword-sdk-go | v0.4.1-beta.1 | go.mod |
| Go | github.com/byteness/go-keychain | v0.0.0-20191008050251-8e49817e8af4 | go.mod |
| Go | github.com/byteness/go-libsecret | v0.0.0-20260108215642-107379d3dee0 | go.mod |
| Go | github.com/byteness/percent | v0.2.2 | go.mod |
| Go | github.com/danieljoos/wincred | v1.2.3 | go.mod |
| Go | github.com/dvsekhvalnov/jose2go | v1.8.0 | go.mod |
| Go | github.com/godbus/dbus/v5 | v5.2.2 | go.mod |
| Go | github.com/noamcohen97/touchid-go | v0.3.0 | go.mod |
| Go | github.com/stretchr/testify | v1.11.1 | go.mod |
| Go | golang.org/x/sys | v0.47.0 | go.mod |
| Go | golang.org/x/term | v0.45.0 | go.mod |
| Go | google.golang.org/protobuf | v1.36.11 | go.mod |
All dependencies 29
Full resolved dependency set from the GitHub dependency graph: 13 direct and 16 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| Go | github.com/1password/connect-sdk-go | v1.5.4-0.20250417152128-c154b387248b | direct |
| Go | github.com/1password/onepassword-sdk-go | v0.4.1-beta.1 | direct |
| Go | github.com/byteness/go-keychain | v0.0.0-20191008050251-8e49817e8af4 | direct |
| Go | github.com/byteness/go-libsecret | v0.0.0-20260108215642-107379d3dee0 | direct |
| Go | github.com/byteness/percent | v0.2.2 | direct |
| Go | github.com/danieljoos/wincred | v1.2.3 | direct |
| Go | github.com/dvsekhvalnov/jose2go | v1.8.0 | direct |
| Go | github.com/godbus/dbus/v5 | v5.2.2 | direct |
| Go | github.com/noamcohen97/touchid-go | v0.3.0 | direct |
| Go | github.com/stretchr/testify | v1.11.1 | direct |
| Go | golang.org/x/sys | v0.47.0 | direct |
| Go | golang.org/x/term | v0.45.0 | direct |
| Go | google.golang.org/protobuf | v1.36.11 | direct |
| Go | github.com/davecgh/go-spew | v1.1.1 | indirect |
| Go | github.com/dylibso/observe-sdk/go | v0.0.0-20240828172851-9145d8ad07e1 | indirect |
| Go | github.com/extism/go-sdk | v1.7.1 | indirect |
| Go | github.com/gobwas/glob | v0.2.3 | indirect |
| Go | github.com/ianlancetaylor/demangle | v0.0.0-20251118225945-96ee0021ea0f | indirect |
| Go | github.com/opentracing/opentracing-go | v1.2.0 | indirect |
| Go | github.com/pkg/errors | v0.9.1 | indirect |
| Go | github.com/pmezard/go-difflib | v1.0.0 | indirect |
| Go | github.com/stretchr/objx | v0.5.2 | indirect |
| Go | github.com/tetratelabs/wabin | v0.0.0-20230304001439-f6f874872834 | indirect |
| Go | github.com/tetratelabs/wazero | v1.11.0 | indirect |
| Go | github.com/uber/jaeger-client-go | v2.30.0+incompatible | indirect |
| Go | github.com/uber/jaeger-lib | v2.4.1+incompatible | indirect |
| Go | go.opentelemetry.io/proto/otlp | v1.9.0 | indirect |
| Go | go.uber.org/atomic | v1.11.0 | indirect |
| Go | gopkg.in/yaml.v3 | v3.0.1 | indirect |
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.
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.12.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Go.