Score7.7
Popularity0.0
Risklow
TierSilver
Score breakdown
Usefulness8.0
Novelty8.0
Momentum7.0
Maturity5.6
Open-source/build8.4
Evidence7.2
Workflow potential8.8
Setup ease6.4
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most multi-agent system architects today who need an agent work ledger wire a custom event log (one for source, one for destination, one for timestamp, one for message type), write a custom serialization layer for cross-language sharing, write a custom trust layer for 'facts before trust', and rebuild the agent work ledger on every project. kungfu-systems/kungfu inverts that pattern: a single Apac
Who should use it
Multi-agent system architects, AI agent developers, low-latency-system developers, C++/Python/Node.js users, journal / event-log users, AI-curious readers tracking the journal-first-runtime space, engineering teams wiring agent work ledgers to their multi-language codebase, and any developer wiring a journal-first agent work ledger + zero-copy multi-language runtime (C++ + Python + Node) + facts-before-trust to their agent workflow -- and who can pair kungfu-systems/kungfu with the `kungfu-code` CLI for the CLI surface, the `kungfu-code.cmd` for the Windows CLI surface, the `kungfu-code.mjs` for the Node.js entry-point surface, the `framework/core/yijinjing` for the journal-first-data-plane surface, the `framework/core/longfist` for the unified-type-system surface, the C++ runtime for the C++ surface, the Python runtime for the Python surface, the Node N-API runtime for the Node surface, the `framework/api/` for the API surface, the `framework/config/` for the config surface, the `framework/contract/` for the contract surface, the `framework/gui/` for the GUI surface, the `framework/kfx/` for the KFX surface, the `framework/release/` for the release surface, the `framework/skill/` for the skill surface, the `framework/spec/` for the spec surface, the `framework/tui/` for the TUI surface, the `examples/` for the reference-applications surface, the `extensions/` for the extensions surface, the `developer/` for the developer-tools surface, the `docs/` for the docs surface, the `scripts/` for the build-scripts surface, the `AGENTS.md` for the agent-instructions surface, the `CONTRIBUTING.md` for the contribution surface, the `SECURITY.md` for the security surface, the `LICENSE-POLICY.md` for the license-policy surface, the `PROVIDER_COMPLIANCE.md` for the provider-compliance surface, the `ACCEPTABLE_USE.md` for the acceptable-use surface, the `TRADEMARK.md` for the trademark surface, the `THIRD_PARTY_NOTICES.md` for the third-party-notices surface, and a target journal-first agent work ledger workflow (event log + zero-copy + facts-before-trust) for the eval surfaceMulti-agent system architects + AI agent developers that want the journal-first data plane (one append-only event log with a unified type system carrying source / destination / nanosecond timestamp / message type) -- the right event-log primitive for any multi-agent system architect who has been writing a custom event logMulti-agent system architects + low-latency-system developers that want the zero-copy multi-language runtime (the same in-process journal data is shared across C++ + Python + Node N-API without serialization on the hot path) -- the right zero-copy-ergonomics primitive for any multi-agent system architect who has been writing a custom serialization layerMulti-agent system architects + trust-conscious users that want the facts-before-trust (every load-bearing claim should be bound to a verifiable source, artifact, manifest, or runtime receipt) -- the right trust-primitive for any multi-agent system architect who has been writing a custom trust layerMulti-agent system architects + SDK users that want the open-core (the open-source core, SDK surface, and reference applications are open; the commercial product surface is 'coming soon') -- the right open-core primitive for any multi-agent system architect who has been writing a custom SDKMulti-agent system architects + CLI users that want the CLI `kungfu-code` (the consumer uses the `kungfu-code` CLI to interact with the journal) + the 10 framework subdirs (api + config + contract + core + gui + kfx + release + skill + spec + tui) + the examples/ + the extensions/ + the developer/ + the docs/ + the scripts/ + the AGENTS.md + the CONTRIBUTING.md + the SECURITY.md + the LICENSE-POLICY.md + the PROVIDER_COMPLIANCE.md + the ACCEPTABLE_USE.md + the TRADEMARK.md + the THIRD_PARTY_NOTICES.md + the 4-field corroboration (forks 1208, size 213850KB, subscribers 275, pushed 2026-07-08) + Apache-2.0 -- the right CLI + install-friction + transparency + compliance-primitive for any multi-agent system architect who has been writing a custom CLI
Who should skip it
Skip Kungfu: Journal-First Agent Work Ledger with Zero-Copy Multi-Language Runtime unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
Kungfu: Journal-First Agent Work Ledger with Zero-Copy Multi-Language Runtime is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, Kungfu: Journal-First Agent Work Ledger with Zero-Copy Multi-Language Runtime is strongest on workflow potential (8.8) and open-source/build quality (8.4) and weakest on maturity (5.6) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Kungfu: Journal-First Agent Work Ledger with Zero-Copy Multi-Language Runtime a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
The 3881* / 1208-fork / 275-subscriber / 213850KB repo is at active maintenance (pushed 2026-07-08) but the project is the open-core runtime -- the commercial product surface is 'coming soon' (the open-source runtime + SDK + reference applications are open; the consumer SHOULD review the commercial product roadmap before adopting in production); the consumer SHOULD review the `docs/` directory before adopting; the consumer SHOULD pin the Kungfu version and review the changelog.
Evidence links
Closest alternatives / related signals
open-sourceapache-2-0kungfukungfu-systemsagent-work-ledgerjournal-firstyijinjinglongfist
