4 findingsStatic scanned
Puts Claude in your terminal to understand your codebase, edit files and handle git workflows.
80.2M installs/moSEE LICENSE IN README.md
Usekibble CLI
usekibble · App
Kibble is a usage dashboard for AI coding agents, and this is its open-source collector. It reads the usage logs that Claude Code, Codex and GitHub Copilot already write on your machine and pushes a per-day summary to your Kibble dashboard, so you can see what each agent spent per person, team, model and repository. Logging in links the machine to your Kibble account, and team plans add shared scopes, roles and invitations.
Written by ooruby from the README of @usekibble/cli 0.9.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You can see what each coding agent spent, per person, team, model and repository, using logs already on your machine.
What you could do with it
- Check which local agent logs it can read before you link an account.
- Preview the counts-only payload with a dry run before anything is sent to your dashboard.
- Pull up your own agent usage for the past week from the terminal once you have logged in.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
The Kibble collector: reports Claude Code, Codex and Copilot usage, per engineer, team, model and repo. Counts only, never prompts, code or paths.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.9.1, the file with digest sha512-rOJwbj43k2H+3ZfsAKw6fr6Ef6LheEnsdnaamcIdDHsGyWa9cuTET4s1Q7WIk8eW7G3NSZX8ZMvw1BAlNoHB6g==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @usekibble/cli@0.9.1Pinned to 0.9.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @usekibble/cli
- Version read
- 0.9.1
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/usekibble/cli
- Commit
- 6412bc59730a
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/usekibble-cli)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-08
Similar apps
All appsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.