bwt
// tools · vendor health

Vendor health

Composite activity score per vendor: last release date, release cadence, blog publishing, and live product breadth — with verified deprecations weighted above all of it. Sorted by abandonment risk so you can derisk a premium purchase before clicking buy.

// ranked
// methodology

Scoring

Four 0-25 buckets summed. Recency of last release, release count in 90 days, blog posts in 90 days, and breadth of live products in our directory. The worst-performing axis still affects the total, so a vendor cannot ride a single signal to a top score.

Verified status overrides activity

The four buckets are heuristics inferred from activity. Where we have verified a product as deprecated or abandoned — usually from the vendor's own statement — that fact outranks them: it deducts from the score in proportion to how much of the catalogue is dead, and those products stop counting toward breadth. If every product we track from a vendor is dead, they are scored as risk no matter how active the blog is.

Data freshness

Release data pulls from each product's tracked changelog. Blog feeds refresh on every build via the vendor RSS aggregation. Scores are computed at build time and reflect the build moment.