Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 15:27 UTC

vibecook-dev / truffle

Simple network programming on top of Tailscale.

RustMIT★ 1 star⑂ 0 forkssince Feb 2026View on GitHub ↗
KindLibraryTerminal interfaceCommand-line toolDesktop applicationhow this is determined
#cli#cross-platform#mesh-networking#p2p#rust#tailscale#websocket#local-first#networking#nodejs#typescript

vibecook-dev/truffle holds a health index of 73 out of 100, placing it in the Good band. It scores highest on AI Readiness (92/100) and lowest on Community & Adoption (33/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

vibecookOrganization
1 follower6 public repossince Jul 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iotruffle0.7.13116366 days agomeshnetworkingp2ptailscalenetwork-programming
npm@vibecook/truffle0.7.13475336 days agomeshnetworkingtailscalelocal-firstp2pnapirust
npm@vibecook/truffle-react0.7.13352336 days agomeshnetworkingtailscalelocal-firstp2preacthooks
Gogithub.com/vibecook-dev/trufflev0.7.13-96 days ago—
crates.iotruffle-core0.7.13395366 days ago—

Metrics by category

Vitality

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

80Excellent · 21% of overall

Development activity

74Good
How it's scored
36/36Push recency — last push 4 days ago
10.4/36Commit cadence — 15/52 weeks with commits
18/18Commit volume — 509 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year509
human_commit_share0.68
days_since_last_push4
active_weeks_last_year15

Release discipline

90Excellent
How it's scored
27/27Ships releases — 61 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~5 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count61
latest_release_tagtailscalekit-59d4bb82-ts1.102.3-go1.26.8-r2
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases5

Community & Adoption

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

33At Risk · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 1 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

57Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Ecosystem adoption (downloads)

52Moderate
How it's scored
41.7/80Monthly downloads — 1,338 downloads/month across crates, go, npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestruffle, @vibecook/truffle, @vibecook/truffle-react, github.com/vibecook-dev/truffle, truffle-core
dependents—
ecosystemscrates, go, npm
total_downloads2,199
monthly_downloads1,338
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

54Moderate · 23% of overall

Maintainer resilience (bus factor)

16Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1

Issue & PR responsiveness

77Good
How it's scored
42/42Issue resolution — 100% of issues closed
24.7/30PR acceptance — 141/171 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/22 approved changesets -- score normalized to 0
Inputs used
merged_prs141
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs30
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.

Ownership & stewardship

39Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
2.2/25Owner reach — 1 followers of vibecook-dev
6.4/25Track record — 6 public repos, account ~0 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginvibecook-dev
public_repos6
account_age_days48

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 5 package(s) on crates, go, npm
35/35Publish recency — latest publish 6 days ago
20/20Version history — 36 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestruffle, @vibecook/truffle, @vibecook/truffle-react, github.com/vibecook-dev/truffle, truffle-core
ecosystemscrates, go, npm
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([workspace.lints]), crates/truffle-bench/Cargo.toml ([lints]), crates/truffle-cli/Cargo.toml ([lints]), crates/truffle-core/Cargo.toml ([lints]), crates/truffle-napi/Cargo.toml ([lints]), crates/truffle-sidecar/Cargo.toml ([lints]), crates/truffle-tauri-plugin/Cargo.toml ([lints]), crates/truffle/Cargo.toml ([lints]), eslint.config.js, rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 18 out of 18 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://vibecook-dev.github.io/truffle/
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicscli, cross-platform, mesh-networking, p2p, rust, tailscale, websocket, local-first, networking, nodejs, typescript
has_wikiyes
homepagehttps://vibecook-dev.github.io/truffle/
docs_sitehttps://vibecook-dev.github.io/truffle/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 16% of overall

Security posture

53Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 18 out of 18 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/22 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
4.5/5SAST — SAST tool detected but not run on all commits
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 — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 86 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.3

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.

92Excellent · 4% of overall

Agent context & guidance

85Excellent
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 68 of 68 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes3,444

Verify loop (build / test / typecheck)

92Excellent
How it's scored
18/18One-command bootstrap — justfile
22/22Automated tests
11/11Lint / format config — Cargo.toml ([workspace.lints]), crates/truffle-bench/Cargo.toml ([lints]), crates/truffle-cli/Cargo.toml ([lints]), crates/truffle-core/Cargo.toml ([lints]), crates/truffle-napi/Cargo.toml ([lints]), crates/truffle-sidecar/Cargo.toml ([lints]), crates/truffle-tauri-plugin/Cargo.toml ([lints]), crates/truffle/Cargo.toml ([lints]), eslint.config.js, rustfmt.toml
11/11Static type checking — examples/chat/tsconfig.json, examples/discovery/tsconfig.json, examples/expose-dev-server/tsconfig.json, examples/express-over-mesh/tsconfig.json, examples/netcat/tsconfig.json, examples/playground/tsconfig.json, examples/quic-streams/tsconfig.json, examples/serve-static-spa/tsconfig.json, examples/shared-state/tsconfig.json, examples/ws-chat-over-mesh/tsconfig.json, packages/cli/tsconfig.json, packages/core/tsconfig.json, packages/react/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 31 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, go.sum, package-lock.json, pnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_filesjustfile
has_devcontainerno
has_linter_configyes
typecheck_configsexamples/chat/tsconfig.json, examples/discovery/tsconfig.json, examples/expose-dev-server/tsconfig.json, examples/express-over-mesh/tsconfig.json, examples/netcat/tsconfig.json, examples/playground/tsconfig.json, examples/quic-streams/tsconfig.json, examples/serve-static-spa/tsconfig.json, examples/shared-state/tsconfig.json, examples/ws-chat-over-mesh/tsconfig.json, packages/cli/tsconfig.json, packages/core/tsconfig.json, packages/react/tsconfig.json, tsconfig.json
agent_commit_share0.31
toolchain_manifestsCargo.toml, apple/Vendor/libtailscale/go.mod, crates/truffle-bench/Cargo.toml, crates/truffle-cli/Cargo.toml, crates/truffle-core/Cargo.toml, crates/truffle-napi/Cargo.toml, crates/truffle-sidecar/Cargo.toml, crates/truffle-tauri-plugin/Cargo.toml, crates/truffle/Cargo.toml, packages/sidecar-slim/go.mod
dependency_bot_commit_share0

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
54/55Manageable file sizes — 5/263 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes133,875
source_files_sampled263
oversized_source_files5

Machine-readable interfaces

100Exceptional
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

1GitHub stars
1contributors
509commits, last 12 months
4days since last push
61releases
1bus factor
0open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'truffle-cli' from its registry
  • Could not fetch crates package 'truffle-napi' from its registry
  • Could not fetch crates package 'truffle-bench' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-12 15:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests18 out of 18 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/22 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities86 existing vulnerabilities detected
Direct dependencies 86
RegistryPackageVersion constraintManifest
crates.iotruffle-core—crates/truffle-bench/Cargo.toml
crates.iotokio—crates/truffle-bench/Cargo.toml
crates.ioclap—crates/truffle-bench/Cargo.toml
crates.ioserde—crates/truffle-bench/Cargo.toml
crates.ioserde_json—crates/truffle-bench/Cargo.toml
crates.iotracing—crates/truffle-bench/Cargo.toml
crates.iotracing-subscriber—crates/truffle-bench/Cargo.toml
crates.iohdrhistogram—crates/truffle-bench/Cargo.toml
crates.iodotenvy—crates/truffle-bench/Cargo.toml
crates.iotempfile—crates/truffle-bench/Cargo.toml
crates.iouuid—crates/truffle-bench/Cargo.toml
crates.iosha2—crates/truffle-bench/Cargo.toml
crates.iochrono—crates/truffle-bench/Cargo.toml
crates.iotruffle-core—crates/truffle-cli/Cargo.toml
crates.ioclap—crates/truffle-cli/Cargo.toml
crates.iotokio—crates/truffle-cli/Cargo.toml
crates.ioserde—crates/truffle-cli/Cargo.toml
crates.ioserde_json—crates/truffle-cli/Cargo.toml
crates.iotoml—crates/truffle-cli/Cargo.toml
crates.iodirs—crates/truffle-cli/Cargo.toml
crates.iotracing—crates/truffle-cli/Cargo.toml
crates.iotracing-subscriber—crates/truffle-cli/Cargo.toml
crates.iouuid—crates/truffle-cli/Cargo.toml
crates.iohostname—crates/truffle-cli/Cargo.toml
crates.iosha2—crates/truffle-cli/Cargo.toml
crates.iohex—crates/truffle-cli/Cargo.toml
crates.ioreqwest—crates/truffle-cli/Cargo.toml
crates.ioflate2—crates/truffle-cli/Cargo.toml
crates.iotar—crates/truffle-cli/Cargo.toml
crates.iofutures-util—crates/truffle-cli/Cargo.toml
crates.iotempfile—crates/truffle-cli/Cargo.toml
crates.iochrono—crates/truffle-cli/Cargo.toml
crates.iounicode-segmentation—crates/truffle-cli/Cargo.toml
crates.iounicode-width—crates/truffle-cli/Cargo.toml
crates.ioratatui—crates/truffle-cli/Cargo.toml
crates.iocrossterm—crates/truffle-cli/Cargo.toml
crates.iofutures—crates/truffle-cli/Cargo.toml
crates.ioopen—crates/truffle-cli/Cargo.toml
crates.ioratatui-explorer—crates/truffle-cli/Cargo.toml
crates.iotokio—crates/truffle-core/Cargo.toml
crates.ioserde—crates/truffle-core/Cargo.toml
crates.ioserde_json—crates/truffle-core/Cargo.toml
crates.iotracing—crates/truffle-core/Cargo.toml
crates.iohex—crates/truffle-core/Cargo.toml
crates.iobase64—crates/truffle-core/Cargo.toml
crates.iogetrandom—crates/truffle-core/Cargo.toml
crates.iosubtle—crates/truffle-core/Cargo.toml
crates.iouuid—crates/truffle-core/Cargo.toml
crates.iothiserror—crates/truffle-core/Cargo.toml
crates.iotokio-tungstenite—crates/truffle-core/Cargo.toml
crates.iofutures-util—crates/truffle-core/Cargo.toml
crates.iotokio-util—crates/truffle-core/Cargo.toml
crates.ioquinn—crates/truffle-core/Cargo.toml
crates.iorustls—crates/truffle-core/Cargo.toml
crates.iorcgen—crates/truffle-core/Cargo.toml
crates.iosha2—crates/truffle-core/Cargo.toml
crates.ioulid—crates/truffle-core/Cargo.toml
crates.iodirs—crates/truffle-core/Cargo.toml
crates.iounicode-normalization—crates/truffle-core/Cargo.toml
crates.iodeunicode—crates/truffle-core/Cargo.toml
crates.ioblake3—crates/truffle-core/Cargo.toml
crates.iohostname—crates/truffle-core/Cargo.toml
crates.iotruffle-core—crates/truffle-napi/Cargo.toml
crates.ionapi—crates/truffle-napi/Cargo.toml
crates.ionapi-derive—crates/truffle-napi/Cargo.toml
crates.ioquinn—crates/truffle-napi/Cargo.toml
crates.ioserde_json—crates/truffle-napi/Cargo.toml
crates.iotokio—crates/truffle-napi/Cargo.toml
crates.iotracing—crates/truffle-napi/Cargo.toml
crates.iotruffle-core—crates/truffle-tauri-plugin/Cargo.toml
crates.iotauri—crates/truffle-tauri-plugin/Cargo.toml
crates.iotauri-plugin—crates/truffle-tauri-plugin/Cargo.toml
crates.ioserde—crates/truffle-tauri-plugin/Cargo.toml
crates.ioserde_json—crates/truffle-tauri-plugin/Cargo.toml
crates.iotokio—crates/truffle-tauri-plugin/Cargo.toml
crates.ioquinn—crates/truffle-tauri-plugin/Cargo.toml
crates.iouuid—crates/truffle-tauri-plugin/Cargo.toml
crates.iotracing—crates/truffle-tauri-plugin/Cargo.toml
crates.iotruffle-core0.7.13crates/truffle/Cargo.toml
crates.iotruffle-sidecar0.7.13crates/truffle/Cargo.toml
npm@vibecook/truffleworkspace:*packages/cli/package.json
npmcitty^0.2.2packages/cli/package.json
npmconsola^3.4.0packages/cli/package.json
npm@vibecook/truffle-nativeworkspace:*packages/core/package.json
npm@vibecook/truffleworkspace:*packages/react/package.json
Gotailscale.comv1.102.3packages/sidecar-slim/go.mod
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with vibecook-dev/truffle. Read them side by side →

98valkey-io/valkey-glideAn open source Valkey client library that supports Valkey, and Redis open source 6.2, 7.0 and 7.2. Valkey GLIDE is designed for reliability, optimized performance, and high-availability, for Valkey and Redis OSS based applications. GLIDE is a multi language client library, written in Rust with programming language bindings, such as Java and PythonExceptional98nrwl/nxThe Monorepo Platform that amplifies both developers and AI agents. Nx optimizes your builds, scales your CI, and fixes failed PRs automatically. Ship in half the time.Exceptional98slackapi/node-slack-sdkSlack Developer Kit for Node.jsExceptional98svix/svix-webhooksThe open source and enterprise-ready webhooks service 🦀Exceptional99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional100clerk/javascriptOfficial JavaScript repository for Clerk authenticationExceptional

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 — crates.io, npm, Go.