Skip to content

codetruss 0.2.50 - #16

Merged
DeliriumPulse merged 1 commit into
mainfrom
codetruss-0.2.50
Aug 8, 2026
Merged

codetruss 0.2.50#16
DeliriumPulse merged 1 commit into
mainfrom
codetruss-0.2.50

Conversation

@DeliriumPulse

Copy link
Copy Markdown
Collaborator

Points the formula at the v0.2.50 release archive.

url    https://github.com/CodeTruss/codetruss-cli/releases/download/v0.2.50/codetruss-cli-0.2.50.tgz
sha256 1f5fc0d4633cda7d82f2c07e315496a9608bc15f01aa14cfc10aebbd88c977f5

That digest was measured off the downloaded release asset, not copied from the release notes. The asset cmps byte-identical to public/downloads/codetruss-cli-0.2.50.tgz in the monorepo, to the bytes codetruss.com serves, and to the archive rebuilt independently in the mirror from its own lockfile. gh attestation verify codetruss-cli-0.2.50.tgz --repo CodeTruss/codetruss-cli passes, and the release carries all three attestations: SLSA provenance v1, CycloneDX, and the in-toto release predicate.

The same cmp against 0.2.46 — the version this formula pointed at until now — exits 1, so the comparison is capable of failing.

Nothing else changes. .github/workflows/test.yml derives the expected version from brew info rather than a literal, so it needs no edit; the version assertion in CI is what proves the installed binary matches the formula.

What 0.2.50 is

dead-code spent 26 of a 27-second analysis re-scanning an 18 MB concatenation of the repository once per candidate module, while saturated at its 20-finding cap the whole time — so the scanning bought nothing. It now builds one index of referenced filename stems and answers each candidate with a set lookup. Findings, cap behaviour, completeness flags and pass metrics are byte-identical across four pinned repositories.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@DeliriumPulse
DeliriumPulse merged commit 0efd55c into main Aug 8, 2026
2 checks passed
@DeliriumPulse
DeliriumPulse deleted the codetruss-0.2.50 branch August 8, 2026 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant