npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

linkdoctor

v0.0.0

Published

A simple tool for checking link health of plain text files.

Downloads

1

Readme

Link Doctor 🔗🩺

oclif

no more broken links!

Link Doctor is a little CLI tool that searches for URLs/links in any plain text file, checks their HTTP response codes and reports back any failing ones.

Particularly useful for identifying broken links in READMEs and awesome-lists! 🤓

Features:

  • 📝 Supports any plain text file
  • 🌐 Supports HTTP and HTTPS links
  • 🛠 Options for customizing which status codes are considered successful or failing
  • 📄 Plain text output option for easy integration into other tools and workflows (e.g. CI)
  • 💅🏻 Pretty logs and results
  • 📦 Easy to install and use

By default, any status codes in the 200-299 range are considered successful, any other status code is considered a failure.

Installation

// TODO

Usage

$ linkdoctor
# Run with default options on README.md in current directory

$ linkdoctor <path-to-file>
# Run with default options on a file

$ linkdoctor --fail 201
# Fail on 201 status codes

$ linkdoctor --pass 403
# Consider 403 status codes to be successful

$ linkdoctor --only 200
# Only consider 200 status codes as successful

A full list of options can be found by running linkdoctor --help.

Contributing

// TODO

License

MIT © Julian Schramm