coldpass

Browse / Other

ppigazzini/valgebra

No description on GitHub.

    Works.Tested on 2026-10-27. From the README alone, on Linux with Haiku.

    Post thisGitHub
    Share card: ppigazzini/valgebra works
    The card X shows when you post.Download

    What we checked

    Does it run from the README?Yes. Running in 11:07 on a clean Linux box.The run

    Tested Oct 27, 2026, rev c0ed4c2.

    Full run evidence and history

    Does it do what the README says?2 of 2 claims held up.Evidence

    “Subtyping is set inclusion: bool is a subtype of int”

    Expected True, checked by the README example runner. Got checked 214 example(s), 0 failed.

    “load parses the JSON and returns the value”

    Expected [1, 2, 3], checked by the README example runner. Got checked 214 example(s), 0 failed.

    Which setups did we try?Works with Haiku. Unverified with Luna.Setups

    Linux / Haiku: works, Oct 27, rev c0ed4c2. Linux / Luna: unverified, Oct 27, rev c0ed4c2.

    Needs keys, a login or a browser?No.Details

    None seen

    Is it safe to run?Made outbound HTTPS connections: yes (hosts not recorded) by <guest-path>What we saw

    Review signals across current setups: connection review. 12 listed items (named-host connections, static matches, dependency advisories) are below and do not change this verdict.

    Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 8 distinct locations. 2 attributed processes.

    OSV reports a known vulnerability in this dependency version. filelock 6 findings.

    Reviewed as expected for a test run: attempted writes that failed, so nothing was written.

    Reviewed as expected for a test run: attempted writes that failed, so nothing was written; package managers (cargo) downloaded dependencies over HTTPS; package managers (rustup-init) downloaded dependencies over HTTPS; resolver address lookups that send no data; wrote only to its own open file handles.

    Full event, path and process lists for each observed setup:

    A quiet run is not a safety guarantee.

    Is it maintained?Maintained · 1287 commits in 90 days · 0 merged PRs in 90 days · 0 open issues · 0 open PRsActivity

    actively maintained: last commit 0 days ago; 1287 commits and 0 merged PRs in 90 days; 0 open issues, 0 open PRs; no releases

    Recent commits on GitHub

    Can I show this on my README?Copy the badge.Badge
    ![coldpass](https://coldpass.dev/badge/ppigazzini--valgebra.svg)

    The run

    Oct 27 · rev c0ed4c2
    0:002:004:006:008:0010:0011:07

    Independent test, not endorsed by the project.