Hub · Entwicklung & APIs

Paketwerk

14 veröffentlichte Endpunkt-URLs. Methoden, Preise, Eingaben und Originaldokumentation auf jeder Detailseite.

paket.halowerk.com · Katalogstand 2026-11-01, 15:19 UTC

Endpunkte

1–14 von 14

Paketwerk0,003 USDC
artifact hash
POSThttps://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 no metadata attached. Hex and base64 input are both accepted and normalised, th
Paketwerk0,005 USDC
dependency bloat
POSThttps://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, how many packages appear at more than one version, and the fan-out of the root
Paketwerk0,005 USDC
dependency confusion
POSThttps://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 they call for different actions. Name is free: nobody has taken it, the door is ope
Paketwerk0,005 USDC
dependency graph
POSThttps://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 bundled, and its depth from the root. Depth is computed as the shortest path from the
Paketwerk0,004 USDC
deprecation monitor
POSThttps://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 everything as new — a monitor that cries wolf on day one is not read on day two.
Paketwerk0,003 USDC
lifecycle check
POSThttps://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.
Paketwerk0,005 USDC
maintainer pulse
POSThttps://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 declared licence and the OpenSSF scorecard without any rate limit or account.
Paketwerk0,003 USDC
package freshness
POSThttps://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 median gap between the last ten releases, the ratio of the current silence to t
Paketwerk0,004 USDC
package match
POSThttps://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 together: names repeat across ecosystems and mean different things there, and that
Paketwerk0,003 USDC
package versions
POSThttps://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 alphabetically and not in registry order, so 1.10.0 sorts after 1.9.0 — the mistake th
Paketwerk0,004 USDC
release cadence
POSThttps://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. A long gap: a silence several times the package own median interval, which sugge
Paketwerk0,004 USDC
runtime compat
POSThttps://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 native build scripts are present; for PyPI it is requires_python together with the
Paketwerk0,006 USDC
typosquat radar
POSThttps://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 seven ecosystems have no search API, and the ones that do rank by popularity inste
Paketwerk0,004 USDC
upgrade path
POSThttps://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 stopping at the last release of 3 and the last release of 4, because that is whe