14 Services from paket.halowerk.com

Returns the full, semantically-sorted version history of a package across seven ecosystems, including publication timestamps, deprecation status, and registry default flags.

Scores the cost of depending on a package by analyzing its resolved transitive graph across four metrics—node count, max depth, multi-version conflicts, and root fan-out—returning a grade from A to E with full threshold details.

Normalises and evaluates package runtime compatibility declarations (engines, os, cpu, Python classifiers) to determine where an npm or PyPI package can run.

Returns a composite health signal for an open-source package, combining repository vitality metrics from deps.dev (stars, forks, issues, licence, OpenSSF scorecard) and optional GitHub activity data (last push, recent commits).

Given a current and target version of a package, returns the ordered list of intermediate major-version stops required to safely upgrade without skipping major versions.

Generates plausible typosquatting variants of a package name and checks each one against seven package registries to detect malicious or squatted lookalikes.

Checks internally-used package names against public registries to detect dependency confusion vulnerabilities — flagging names that are unclaimed, taken by unrelated parties, or otherwise at risk.

Scores the maintenance health of a software package by analyzing its release cadence and deprecation status, returning a letter grade from A to E.

Given a product identifier and optional version, returns end-of-support dates, days remaining, LTS status, and latest patch for that release line.

Resolves a file digest (hash) to the released package versions that match it, across multiple ecosystems.

Returns the fully resolved dependency graph for a specific package version, including every transitive dependency node with ecosystem, name, resolved version, bundled status, and BFS-computed depth from root.

Monitors named packages for deprecation changes across registry ecosystems by storing a baseline snapshot and diffing subsequent calls against it to report only new deprecations.

Resolves a package name to the source projects it declares, with provenance for each link, to determine whether packages truly belong together across ecosystems.

Analyzes the release timing history of a package to detect cadence anomalies — specifically long dormancy gaps and burst release clusters — and reports where the pattern breaks.