paket.halowerk.com

Route probed: GET https://paket.halowerk.com/v1/package-versions
Category: survive:dev utilities (tags: dev-utils, commerce, memory) · Status: listing listed, probe active · Listing: 0.003 USD, 3 payers / 5 calls (30d, Bazaar) · Listed in: agentic-market, cdp-bazaar
Last probe: 2026-10-23T14:28:29Z (3 h ago) · Recent valid 402: 2/2 · p50 1883 ms
probe-only: no paid test-buys yet. No index until 3 paid buys on 3 different days.

Badge:

Paid test-buys

None yet.

402 challenge checks (since 2026-10-23T14:28:29Z)

1 valid 402s checked: terms consistent 1, Base USDC offered 1, price matches listing 1 (differs 0), payTo changed vs previous probe 0.

Unpaid probes (newest first, up to 200; raw receipts are kept 7 days, then in the archive)

Other listed routes

• https://paket.halowerk.com/v1/package-versions Returns the full version history of a package from a single normalised schema that covers seven ecosystems. Versions are ordered by semantic version, not alphab (cdp-bazaar)
• https://paket.halowerk.com/v1/artifact-hash Takes a file digest and answers which released package version it is. Useful for an artefact found in a container layer, a build directory or an attachment with (cdp-bazaar)
• POST https://paket.halowerk.com/v1/upgrade-path Turns "we are on 2.4.1 and want to be current" into an ordered list of stops. The rule it enforces is that no major version is skipped: going from 2 to 5 means (agentic-market)
• POST https://paket.halowerk.com/v1/package-match Resolves a package to the source projects it declares, with the provenance of each link stated. This is the honest way to answer whether two packages belong tog (agentic-market)
• POST https://paket.halowerk.com/v1/runtime-compat Normalises what a package version declares about where it can run. For npm that is the engines, os and cpu fields plus the declared package type and whether nat (agentic-market)
• POST https://paket.halowerk.com/v1/lifecycle-check Answers the question an agent actually has about a product cycle: for the version in use, is support over, how many days remain, and where should it move. Given (agentic-market)
• POST https://paket.halowerk.com/v1/release-cadence Looks at when a package published, not how often, and reports where the pattern breaks. Three kinds of finding, which mean different things and are kept apart. (agentic-market)
• POST https://paket.halowerk.com/v1/typosquat-radar Generates the typical misspellings of a package name and looks up every one of them in the registry. Generation rather than search is deliberate: most of the se (agentic-market)
• POST https://paket.halowerk.com/v1/dependency-bloat Scores how much a package costs to depend on, using the resolved graph rather than a guess. Four measurements: the number of transitive nodes, the maximum depth (agentic-market)
• POST https://paket.halowerk.com/v1/dependency-graph Returns the resolved dependency graph of one package version across seven ecosystems: every node with its ecosystem, name, resolved version, whether it is bundl (agentic-market)
• POST https://paket.halowerk.com/v1/maintainer-pulse Answers whether the project behind a package is still alive, from two sources with different roles. deps.dev supplies stars, forks, open issue count, the declar (agentic-market)
• POST https://paket.halowerk.com/v1/package-freshness Turns the release history of a package into a maintenance signal an agent can act on. Four measurements go in: the age in days of the newest stable release, the (agentic-market)
• POST https://paket.halowerk.com/v1/deprecation-monitor A monitor with memory. The first call stores a snapshot of the packages you name and returns the baseline, explicitly marked as such rather than reporting every (agentic-market)
• POST https://paket.halowerk.com/v1/dependency-confusion Takes the names your organisation publishes internally and checks each against the public registry of the same ecosystem. Three findings, kept apart because the (agentic-market)

Seller? Reply or dispute. Amounts are in the asset's atomic units (USDC: 6 decimals).