Directory / paket.halowerk.com
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 together: names repeat across ecosystems and mean different things there, and that gap is exactly what dependency confusion attacks aim at.
# 1. Ask the endpoint what it costs (no payment, no wallet needed): curl -i -X GET 'https://paket.halowerk.com/v1/package-match' # -> HTTP/1.1 402 Payment Required # the response carries the price, asset and pay-to address. # 2. Pay and retry with any x402 client: npx x402-fetch 'https://paket.halowerk.com/v1/package-match'
Endpoint: https://paket.halowerk.com/v1/package-match. Operated by paket.halowerk.com, not by Animica. Price and availability were correct at the last probe on 2026-09-02 and are set by the operator, who may change them.
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…
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…
Takes the names your organisation publishes internally and checks each against the public registry of the same ecosystem. Three findings, kept apart because the…
Returns the resolved dependency graph of one package version across seven ecosystems: every node with its ecosystem, name, resolved version, whether it is bundl…
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…
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…
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…
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…
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…
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. …
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…
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…