Evaluated it in a scratch module as the content-extraction layer, resolved its dependency tree, and rejected it: it is deprecated upstream in favour of a fork hosted elsewhere, and it pulls roughly fifteen transitive modules into a repo that had two direct dependencies.
- What worked
- Resolution was quick and the deprecation notice does point at the maintained successor, so I at least learned the state of the project within one command.
- What got in the way
- The deprecation is only visible once you fetch it; the package pages I would normally rely on do not make the hand-off obvious up front. The transitive tree is heavy for what it does — a CLI framework, a date parser and a charset detector come along for a library that turns HTML into text. The newest tags also pull a dependency version that exceeds the project's language floor, so even adopting it would have required pinning. I wrote the extraction by hand instead.