chore(deps): update dependency pkg-pr-new to ^0.0.75 by renovate[bot] · Pull Request #1149 · ryoppippi/ccusage

renovate · 2026-05-25T00:43:19Z

This PR contains the following updates:

Package	Change	Age	Confidence
pkg-pr-new (source)	`^0.0.60` → `^0.0.75`

Release Notes

stackblitz-labs/pkg.pr.new (pkg-pr-new)

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2026-05-25T00:43:22Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

packages/ccusage-darwin-arm64            | [WARN] Unsupported platform: wanted: {"cpu":["arm64"],"os":["darwin"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
packages/ccusage-darwin-x64              | [WARN] Unsupported platform: wanted: {"cpu":["x64"],"os":["darwin"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
packages/ccusage-linux-arm64             | [WARN] Unsupported platform: wanted: {"cpu":["arm64"],"os":["linux"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
packages/ccusage-win32-arm64             | [WARN] Unsupported platform: wanted: {"cpu":["arm64"],"os":["win32"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
packages/ccusage-win32-x64               | [WARN] Unsupported platform: wanted: {"cpu":["x64"],"os":["win32"],"libc":["any"]} (current: {"os":"linux","cpu":"x64","libc":"glibc"})
Scope: all 9 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 14, reused 0, downloaded 0, added 0

   ╭─────────────────────────────────────────╮
   │                                         │
   │   Update available! 11.1.1 → 11.3.0.    │
   │   Changelog: https://pnpm.io/v/11.3.0   │
   │    To update, run: pnpm add -g pnpm     │
   │                                         │
   ╰─────────────────────────────────────────╯

Progress: resolved 15, reused 0, downloaded 0, added 0
Progress: resolved 19, reused 0, downloaded 1, added 0
Progress: resolved 95, reused 0, downloaded 2, added 0
[ERR_PNPM_TRUST_DOWNGRADE] High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover)

This error happened while installing the dependencies of bumpp@10.2.3
 at c12@3.3.2

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

cloudflare-workers-and-pages · 2026-05-25T00:43:30Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	ccusage-guide	`f5f41a7`	Commit Preview URL Branch Preview URL	May 25 2026, 07:30 PM

socket-security · 2026-05-25T19:12:35Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/pkg-pr-new@0.0.75

View full report

renovate · 2026-05-25T19:16:33Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Update pnpm-lock.yaml after the pkg-pr-new catalog range change so frozen installs see matching workspace catalog metadata. The new pkg-pr-new release removes several transitive dependencies from the lockfile; committing the generated lockfile keeps CI and Cloudflare Workers builds aligned with the Renovate branch.

pkg-pr-new · 2026-05-25T19:33:31Z

Open in StackBlitz

ccusage

npx https://pkg.pr.new/ccusage@1149

@ccusage/ccusage-darwin-arm64

npx https://pkg.pr.new/@ccusage/ccusage-darwin-arm64@1149

@ccusage/ccusage-darwin-x64

npx https://pkg.pr.new/@ccusage/ccusage-darwin-x64@1149

@ccusage/ccusage-linux-arm64

npx https://pkg.pr.new/@ccusage/ccusage-linux-arm64@1149

@ccusage/ccusage-linux-x64

npx https://pkg.pr.new/@ccusage/ccusage-linux-x64@1149

@ccusage/ccusage-win32-arm64

npx https://pkg.pr.new/@ccusage/ccusage-win32-arm64@1149

@ccusage/ccusage-win32-x64

npx https://pkg.pr.new/@ccusage/ccusage-win32-x64@1149

commit: f5f41a7

github-actions · 2026-05-25T19:38:28Z

ccusage performance comparison

PR SHA: 614bbd412a5e
Base SHA: 63cf17e9656a

This compares the Rust PR release binary against the configured base package on the same CI runner.

Package runner startup

Execution setup measures any pre-benchmark package materialization used by the execution benchmark. Bunx temp cache measures one bunx -p <url> ccusage --version run with an empty Bun install cache. Warm reuses that cache and reports the median of repeated runs.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`63cf17e9656a`	517.0ms	508.4ms	34.7ms	3
PR pkg.pr.new	`614bbd4`	687.9ms	642.3ms	34.7ms	3

Cached bunx execution performance

Runs the same large fixture through bunx -p <pkg.pr.new URL> ccusage after the Bun install cache has already been populated by the startup measurement. This separates cached package-runner execution from first-fetch package materialization.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base package: 63cf17e9656a; PR package: 614bbd4. Both run through bunx -p <pkg.pr.new URL> ccusage using the warmed Bun install cache from package runner startup, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	498.1ms	514.9ms	0.97x	253.83 MiB	267.58 MiB	1.05x	2.02 GiB/s	1.96 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	375.6ms	371.8ms	1.01x	60.83 MiB	59.70 MiB	0.98x	2.68 GiB/s	2.71 GiB/s

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	495.0ms	2.03 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	465.2ms	2.16 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	359.7ms	2.80 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	331.6ms	3.04 GiB/s	1

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs rust/target/release/ccusage directly. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	31.1ms	4.2ms	7.37x	43.73 MiB	2.83 MiB	0.06x	0.05 MiB/s	0.37 MiB/s
`claude session --offline --json`	31.5ms	4.3ms	7.38x	43.61 MiB	2.83 MiB	0.06x	0.05 MiB/s	0.36 MiB/s
`codex daily --offline --json`	31.1ms	3.9ms	7.99x	43.48 MiB	2.83 MiB	0.07x	0.03 MiB/s	0.22 MiB/s
`codex session --offline --json`	31.4ms	3.9ms	7.96x	43.61 MiB	2.83 MiB	0.06x	0.03 MiB/s	0.22 MiB/s

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs rust/target/release/ccusage directly. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	493.8ms	473.4ms	1.04x	264.58 MiB	267.70 MiB	1.01x	2.04 GiB/s	2.13 GiB/s
`codex --offline --json`	1.01 GiB	399.1ms	338.9ms	1.18x	64.95 MiB	66.45 MiB	1.02x	2.52 GiB/s	2.97 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.22 KiB	-0.03 KiB	1.00x
installed native package binary	3289.49 KiB	3289.49 KiB	+0.00 KiB	1.00x

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

github-actions · 2026-05-25T19:42:36Z

ccusage performance comparison

PR SHA: 614bbd412a5e
Base SHA: 63cf17e9656a

This compares the PR package against the configured base package on the same CI runner.

Package runner startup

Execution setup measures any pre-benchmark package materialization used by the execution benchmark. Bunx temp cache measures one bunx -p <url> ccusage --version run with an empty Bun install cache. Warm reuses that cache and reports the median of repeated runs.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`63cf17e9656a`	455.7ms	544.2ms	35.2ms	3
PR pkg.pr.new	`614bbd4`	1.060s	695.9ms	34.0ms	3

Cached bunx execution performance

Runs the same large fixture through bunx -p <pkg.pr.new URL> ccusage after the Bun install cache has already been populated by the startup measurement. This separates cached package-runner execution from first-fetch package materialization.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base package: 63cf17e9656a; PR package: 614bbd4. Both run through bunx -p <pkg.pr.new URL> ccusage using the warmed Bun install cache from package runner startup, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	497.9ms	509.6ms	0.98x	292.33 MiB	249.08 MiB	0.85x	2.02 GiB/s	1.98 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	380.2ms	381.7ms	1.00x	60.58 MiB	57.58 MiB	0.95x	2.65 GiB/s	2.64 GiB/s

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	503.4ms	2.00 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	479.5ms	2.10 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	371.3ms	2.71 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	333.2ms	3.02 GiB/s	1

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	31.1ms	31.3ms	0.99x	43.61 MiB	43.36 MiB	0.99x	0.05 MiB/s	0.05 MiB/s
`claude session --offline --json`	31.6ms	31.6ms	1.00x	43.73 MiB	43.48 MiB	0.99x	0.05 MiB/s	0.05 MiB/s
`codex daily --offline --json`	31.2ms	30.9ms	1.01x	43.61 MiB	43.48 MiB	1.00x	0.03 MiB/s	0.03 MiB/s
`codex session --offline --json`	30.6ms	30.5ms	1.00x	-	43.48 MiB	-	0.03 MiB/s	0.03 MiB/s

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	512.4ms	503.0ms	1.02x	249.83 MiB	262.83 MiB	1.05x	1.96 GiB/s	2.00 GiB/s
`codex --offline --json`	1.01 GiB	367.4ms	366.2ms	1.00x	-	51.33 MiB	-	2.74 GiB/s	2.75 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.22 KiB	-0.03 KiB	1.00x
installed native package binary	3289.49 KiB	3289.49 KiB	+0.00 KiB	1.00x

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

github-actions · 2026-05-25T20:01:36Z

ccusage performance comparison

PR SHA: f5f41a78aa08
Base SHA: f7f7be5b32ae

This compares the Rust PR release binary against the configured base package on the same CI runner.

Package runner startup

Execution setup measures any pre-benchmark package materialization used by the execution benchmark. Bunx temp cache measures one bunx -p <url> ccusage --version run with an empty Bun install cache. Warm reuses that cache and reports the median of repeated runs.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`f7f7be5b32ae`	647.7ms	568.1ms	33.7ms	3
PR pkg.pr.new	`f5f41a7`	804.5ms	560.5ms	33.4ms	3

Cached bunx execution performance

Runs the same large fixture through bunx -p <pkg.pr.new URL> ccusage after the Bun install cache has already been populated by the startup measurement. This separates cached package-runner execution from first-fetch package materialization.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base package: f7f7be5b32ae; PR package: f5f41a7. Both run through bunx -p <pkg.pr.new URL> ccusage using the warmed Bun install cache from package runner startup, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	504.1ms	511.0ms	0.99x	255.83 MiB	264.70 MiB	1.03x	2.00 GiB/s	1.97 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	424.5ms	368.8ms	1.15x	63.33 MiB	67.20 MiB	1.06x	2.37 GiB/s	2.73 GiB/s

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	509.8ms	1.97 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	475.1ms	2.12 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	366.3ms	2.75 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	334.4ms	3.01 GiB/s	1

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs rust/target/release/ccusage directly. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	30.9ms	4.1ms	7.60x	43.48 MiB	2.83 MiB	0.07x	0.05 MiB/s	0.38 MiB/s
`claude session --offline --json`	31.5ms	4.0ms	7.89x	43.48 MiB	2.83 MiB	0.07x	0.05 MiB/s	0.39 MiB/s
`codex daily --offline --json`	30.6ms	3.8ms	8.07x	-	2.83 MiB	-	0.03 MiB/s	0.23 MiB/s
`codex session --offline --json`	30.4ms	3.8ms	8.05x	43.48 MiB	2.83 MiB	0.07x	0.03 MiB/s	0.23 MiB/s

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs rust/target/release/ccusage directly. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	505.7ms	472.1ms	1.07x	262.20 MiB	284.20 MiB	1.08x	1.99 GiB/s	2.13 GiB/s
`codex --offline --json`	1.01 GiB	359.8ms	328.9ms	1.09x	51.58 MiB	59.95 MiB	1.16x	2.80 GiB/s	3.06 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.22 KiB	-0.03 KiB	1.00x
installed native package binary	3289.49 KiB	3289.49 KiB	+0.00 KiB	1.00x

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

github-actions · 2026-05-25T20:04:11Z

ccusage performance comparison

PR SHA: f5f41a78aa08
Base SHA: f7f7be5b32ae

This compares the PR package against the configured base package on the same CI runner.

Package runner startup

Execution setup measures any pre-benchmark package materialization used by the execution benchmark. Bunx temp cache measures one bunx -p <url> ccusage --version run with an empty Bun install cache. Warm reuses that cache and reports the median of repeated runs.

Package	SHA	Execution setup	Bunx temp cache	Bunx warm median	Warm samples
Base pkg.pr.new	`f7f7be5b32ae`	400.0ms	601.2ms	34.1ms	3
PR pkg.pr.new	`f5f41a7`	720.5ms	992.4ms	34.6ms	3

Cached bunx execution performance

Runs the same large fixture through bunx -p <pkg.pr.new URL> ccusage after the Bun install cache has already been populated by the startup measurement. This separates cached package-runner execution from first-fetch package materialization.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base package: f7f7be5b32ae; PR package: f5f41a7. Both run through bunx -p <pkg.pr.new URL> ccusage using the warmed Bun install cache from package runner startup, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`bunx -p <pkg> ccusage claude --offline --json`	1.01 GiB	515.1ms	522.6ms	0.99x	271.33 MiB	273.70 MiB	1.01x	1.95 GiB/s	1.93 GiB/s
`bunx -p <pkg> ccusage codex --offline --json`	1.01 GiB	374.9ms	374.7ms	1.00x	61.20 MiB	60.83 MiB	0.99x	2.69 GiB/s	2.69 GiB/s

Package runtime diagnostics

Compares the PR package wrapper, the installed native optional dependency binary, and the workspace release binary on the same large fixture. This identifies whether slow package results come from JavaScript wrapper overhead, the published native binary build, or the Rust core itself.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
All rows run --offline --json, measured by hyperfine with 0 warmups and 1 runs. This isolates wrapper overhead from the installed native optional dependency and the workspace release binary built on the runner.

Command	Runtime	Input	Median	Throughput	Samples
`claude --offline --json`	Package wrapper	1.01 GiB	511.6ms	1.97 GiB/s	1
`claude --offline --json`	Installed native binary	1.01 GiB	480.7ms	2.09 GiB/s	1
`codex --offline --json`	Package wrapper	1.01 GiB	373.8ms	2.69 GiB/s	1
`codex --offline --json`	Installed native binary	1.01 GiB	344.0ms	2.93 GiB/s	1

Committed fixture performance

Committed small fixtures for stable PR-to-PR feedback and explicit Claude/Codex command coverage.

Fixtures: Claude apps/ccusage/test/fixtures/claude (0.00 MiB, 2 files), Codex apps/ccusage/test/fixtures/codex (0.00 MiB, 1 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 2 warmups and 7 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude daily --offline --json`	31.9ms	31.8ms	1.00x	43.48 MiB	43.48 MiB	1.00x	0.05 MiB/s	0.05 MiB/s
`claude session --offline --json`	32.3ms	32.3ms	1.00x	43.48 MiB	43.61 MiB	1.00x	0.05 MiB/s	0.05 MiB/s
`codex daily --offline --json`	31.7ms	31.6ms	1.00x	43.61 MiB	43.61 MiB	1.00x	0.03 MiB/s	0.03 MiB/s
`codex session --offline --json`	31.6ms	31.3ms	1.01x	43.61 MiB	43.48 MiB	1.00x	0.03 MiB/s	0.03 MiB/s

Large real-world-shaped fixture performance

Generated fixtures shaped from aggregate local log statistics: thousands of JSONL files, many small sessions, and a long tail of larger sessions. No real prompts, paths, or outputs are stored in the fixtures.

Fixtures: Claude /home/runner/work/_temp/ccusage-large-fixture (1.01 GiB, 2,597 files), Codex /home/runner/work/_temp/ccusage-large-codex-fixture (1.01 GiB, 2,597 files)
Base runs the published ccusage package from pkg.pr.new, installed before measurement; PR runs the published ccusage package from pkg.pr.new, installed before measurement. Both run --offline --json, measured by hyperfine with 0 warmups and 1 runs.
Peak RSS is measured separately with /usr/bin/time using 1 runs. Lower RSS ratios are better.

Command	Input	Base median	PR median	PR vs base	Base peak RSS	PR peak RSS	PR/base RSS	Base throughput	PR throughput
`claude --offline --json`	1.01 GiB	508.8ms	505.0ms	1.01x	267.58 MiB	256.08 MiB	0.96x	1.98 GiB/s	1.99 GiB/s
`codex --offline --json`	1.01 GiB	363.6ms	411.5ms	0.88x	51.08 MiB	-	-	2.77 GiB/s	2.45 GiB/s

Artifact size

Artifact	Base	PR	Delta	Ratio
packed `ccusage-*.tgz`	14.25 KiB	14.22 KiB	-0.03 KiB	1.00x
installed native package binary	3289.49 KiB	3289.49 KiB	+0.00 KiB	1.00x

Lower medians and smaller artifacts are better. CI runner noise still applies; use same-run ratios as directional PR feedback, not release guarantees.

renovate Bot added dependencies renovate labels May 25, 2026

renovate-approve Bot approved these changes May 25, 2026

View reviewed changes

renovate Bot force-pushed the renovate/pkg-pr-new-0.x branch 4 times, most recently from f1c3235 to 8f0dfdc Compare May 25, 2026 19:01

renovate Bot and others added 2 commits May 25, 2026 20:29

chore(deps): update dependency pkg-pr-new to ^0.0.75

5ff575c

ryoppippi force-pushed the renovate/pkg-pr-new-0.x branch from 614bbd4 to f5f41a7 Compare May 25, 2026 19:29

ryoppippi merged commit 4c00fc3 into main May 25, 2026
29 checks passed

ryoppippi deleted the renovate/pkg-pr-new-0.x branch May 25, 2026 19:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency pkg-pr-new to ^0.0.75#1149

chore(deps): update dependency pkg-pr-new to ^0.0.75#1149
ryoppippi merged 2 commits into
mainfrom
renovate/pkg-pr-new-0.x

renovate Bot commented May 25, 2026 •

edited

Loading

Uh oh!

renovate Bot commented May 25, 2026 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented May 25, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented May 25, 2026 •

edited

Loading

Uh oh!

renovate Bot commented May 25, 2026

Uh oh!

pkg-pr-new Bot commented May 25, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

github-actions Bot commented May 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Configuration

Uh oh!

renovate Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: pnpm-lock.yaml

Uh oh!

cloudflare-workers-and-pages Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

socket-security Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate Bot commented May 25, 2026

Edited/Blocked Notification

Uh oh!

pkg-pr-new Bot commented May 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

github-actions Bot commented May 25, 2026

ccusage performance comparison

Package runner startup

Cached bunx execution performance

Package runtime diagnostics

Committed fixture performance

Large real-world-shaped fixture performance

Artifact size

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented May 25, 2026 •

edited

Loading

renovate Bot commented May 25, 2026 •

edited

Loading

cloudflare-workers-and-pages Bot commented May 25, 2026 •

edited

Loading

socket-security Bot commented May 25, 2026 •

edited

Loading

pkg-pr-new Bot commented May 25, 2026 •

edited

Loading