Browse / Agent tools
scrapinghub/extruct
Extract embedded metadata from HTML markup
Didn’t work.Tested on 2026-10-27. The recorded test did not run successfully. The page shows what happened.
What we checked
Does it run from the README?Didn’t work.The run
Our test failed; no repo verdict.
Tested Oct 27, 2026, rev d24f541.
Does it do what the README says?Not checked yet. It has to run first.Why
We check claims after it’s running.
Which checks were skipped?1 check skipped.Reasons
Skipped checks count as neither passes nor failures.
README claims: 1 skipped
- CLI fetches a page and extracts metadata.: Claim needs an exact quote from source_file (default README.md).
Which setups did we try?Not yet with Luna. Our Haiku test broke, so no mark there.Setups
Linux / Haiku: our test broke. Linux / Luna: not yet, Oct 27, rev d24f541.
Is it safe to run?Made outbound connections: yes (hosts not recorded) by extructWhat we saw
Review signals across current setups: connection review. 6 static matches retained as context.
Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 4 distinct locations. 3 attributed processes.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 13 commits in 90 days · 7 merged PRs in 90 days · 26 open issues · 29 open PRsActivity
actively maintained: last commit 12 days ago; 13 commits and 7 merged PRs in 90 days; 26 open issues, 29 open PRs; 19 of 32 recent threads got a maintainer reply, median first reply 22.2h; no releases
Independent test, not endorsed by the project.