Commit bdcd84c
Add zvelte-check-bin 0.2.0 (#509)
* Add zvelte-check-bin 0.2.0
A fast Svelte diagnostic tool written in Zig, from the ampcode/homebrew-tap
Homebrew formula. First package produced by `pkgmgr import homebrew`.
Prebuilt per-arch binaries from upstream's own GitHub releases. Both
sha256 values were RECOMPUTED from the downloaded bytes rather than
copied out of the formula, so the tap is a cross-check and not the root
of trust for the only value anchoring this package's integrity.
`strip_prefix` is absent because the archives are genuinely flat — read
off the real tarball (`tar -tzf` lists one entry, `zvelte-check`), not
guessed. Homebrew auto-strips a single leading directory before
`def install` and minimal does not, so this is unknowable from the
formula text.
Provenance is derived from the ARTIFACT URLs, which are literally
github.com/ampcode/zvelte-check/releases/..., and cross-checked against
the homepage. That buys real CPE identity (not a dark package) and free
version checking via the GitHub tier.
NOT a source build, and worth stating plainly: `zig` IS packaged, and
pkgs CLAUDE.md prefers building from source when the toolchain exists.
Prebuilt was chosen only because pkgmgr has no Zig BuildFlavor yet — not
because the toolchain is missing. Mitigating: these are upstream's own
release binaries, not a third-party redistribution, and we verify their
hashes ourselves. A source-built `zvelte-check` can take the bare name
later, which is why this one carries the `-bin` suffix.
No reviewer TODOs: licence, provenance, outputs and deps were all
resolved mechanically.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* zvelte-check-bin: drop glibc — the binary is statically linked
Refined against the real built tree with
`pkgmgr import homebrew … --from-build`, which reads the installed ELF
instead of guessing.
The binary is statically linked (`file`: "ELF 64-bit LSB executable,
ARM aarch64 … statically linked"), so it needs no runtime_deps at all.
The discovery-mode `[glibc]` was a template default, not an observation.
Verified by rebuilding: the package produces a new content-addressed
tree and a real 5 MB aarch64 binary at usr/bin/zvelte-check.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* zvelte-check-bin: say it is a binary fetch — `binary_from` (review: @twitchyliquid64)
Tom's read is right: this installs upstream's release binaries, and nothing
in the spec said so. Without `binary_from` the package reads as source-built
from `source_provenance`, which is the same conflation that let chromium-bin
look like a build of microsoft/playwright.
Two halves of the comment, answered separately after checking the source
rather than the formula:
* `binary_from` — added, per arch, naming the exact artifacts we fetch.
* `closed_source` — deliberately NOT set. ampcode/zvelte-check is a public
MIT repo with the Zig source in-tree (LICENSE, build.zig, src/), so
declaring it closed would be false. The formula's silence is not evidence.
`source_provenance` is kept alongside `binary_from`, as chromium-bin does.
Here the two name the SAME project — ampcode builds these artifacts in its
own release workflow — so the repo is the honest identity of the bytes.
Dropping it would cost the CPE identity and the GitHub version-check tier,
i.e. turn a covered package into a dark one.
Verified: `mip check --packages zvelte-check-bin` all Pass, and
`mip dump --packages` resolves binary_from to a real per-arch URL.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>1 parent 62a71f8 commit bdcd84c
2 files changed
Lines changed: 72 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
0 commit comments