Repository navigation
Immutable
release. Only release title and notes can be modified.
The same files as v1.1.0, byte for byte, republished from a tidied commit history.
Much faster on a big transcript folder; the same report, byte for byte.
report.shreads the transcripts with perl when the computer has it (macOS and nearly every
Linux do): one pass over each file, in order, instead of grep and awk. On 1 GB of made-up
transcripts shaped like a heavy user's (scripts/bench-data.mjs) on an Apple silicon Mac, a dry
run went from 49 s to 4 s. Without perl it runs the grep and awk pass of 1.0.0, unchanged; the
tests check both give the golden report.- With
--days N, files last written more than a day before those days began are skipped: a
transcript is only appended to, so they hold none of the rows. - In a terminal, it shows how much of the folder it has read.
report.ps1: only the version changes.
Run it
macOS and Linux (downloads report.sh, checks its SHA-256, then runs it):
curl -fsSLo report.sh https://github.com/shurikenharness/claude-code-usage-dashboard/releases/download/v1.1.1/report.sh && openssl dgst -sha256 -r report.sh | grep -q ^7d8af3eccb2ef2259f0fb165c8f8ca2b55012b07ca632229e684d073e6368e74 && bash report.shWindows PowerShell:
irm "https://github.com/shurikenharness/claude-code-usage-dashboard/releases/download/v1.1.1/report.ps1" -OutFile report.ps1; if ((Get-FileHash report.ps1).Hash -eq 'c70e1c522ae51c9a5137269846759bb83121cc574295877b50aef00b286c2236') { & ([scriptblock]::Create((Get-Content report.ps1 -Raw))) } else { 'report.ps1 does not match its SHA-256, so it was not run.' }Checksums (SHA-256)
7d8af3eccb2ef2259f0fb165c8f8ca2b55012b07ca632229e684d073e6368e74 report.sh
c70e1c522ae51c9a5137269846759bb83121cc574295877b50aef00b286c2236 report.ps1
These files are also signed with a GitHub build attestation:
gh attestation verify report.sh --repo shurikenharness/claude-code-usage-dashboard