Deadlink-Hunter is an open-source project designed to find broken links in GitHub repositories (with future support for other platforms). The goal is to help maintainers keep their documentation clean, reliable, and frustration-free for readers.

Deadlink Hunder Website is the frontend of the website.

You can also check Broken-Link-Checker, this is the backend of the project that check if a link is broken or not.

The project was inspires as a way to give back to the open source community, everyone is welcome.

This is the general design desired for the website, generated by Lovable, just to provide inspiration.

You can check the more elaborated ui that was created with base44 as initial insparation.

In order to see the ui log in.

• The why
• Contributing
• Contributors
• Docker Setup
• Mantine Vite template
• Features
• pnpm scripts
• Build and dev scripts
  • Testing scripts
  • Other scripts

Documentation is the first entry point for most developers exploring a project. Yet, README files and docs often contain outdated or broken links – even in large, well-maintained repositories.

But aren’t there already broken link checkers? There are — but most of them don’t look very good, their UIs are not user-friendly, and their broken link detection doesn’t cover all cases (for example, localhost:4000 is not actually broken).

Contributions are welcome and greatly appreciated!

To contribute:

1. Fork this repository to your own GitHub account.
2. Clone your fork locally:

   git clone [https://github.com/](https://github.com/)<your-username>/Deadlink-Hunter.git
   cd Deadlink-Hunter

3. Install dependencies using pnpm (please do not use npm or yarn):

   pnpm install

4. Create a new branch for your feature or fix:

   git checkout -b my-feature

5. Make your changes and commit them with clear messages.
6. Push your branch to your fork:

   git push origin my-feature

7. Create a Pull Request from your repository’s branch to the main branch of the original repository.

One last thing, We appriciate any one who would like to contribute but please remove the comments in the code that your llm is generating. Its total ok for us to use llm to generate code, and even recommended but lets keep the code clean and commentless.

Thanks to all the amazing contributors who have helped make this project better! 🎉

Install dependencies using pnpm (please do not use npm or yarn):

pnpm install

Create a new branch for your feature or fix:

git checkout -b my-feature

Make your changes and commit them with clear messages.

Push your branch to your fork, and craete pull requests from your repository into the main branch inside the original repository

This project includes Docker support for easy deployment and development. You can run the application using Docker in two ways:

The easiest way to run the application is using Docker Compose:

# Build and start the application
docker-compose up --build

# Or run in detached mode (background)
docker-compose up --build -d

The application will be available at http://localhost

To stop the application:

docker-compose down

You can also build and run the Docker container directly:

# Build the Docker image
docker build -t deadlink-hunter .

# Run the container
docker run -p 80:6006 deadlink-hunter

The application will be available at http://localhost

• Port: The application runs on port 6006 inside the container and is mapped to port 80 on your host machine
• Web Server: Uses nginx to serve the built application
• Build Process: Multi-stage build that installs dependencies, builds the app, and serves it with nginx
• Base Image: Built on node:20-alpine for the build stage and nginx:1.27-alpine for the runtime

This project is based on the Mantine Vite template.

This template comes with the following features:

• PostCSS with mantine-postcss-preset
• TypeScript
• Storybook
• Vitest setup with React Testing Library
• ESLint setup with eslint-config-mantine

• dev – start development server
• build – build production version of the app
• preview – locally preview production build

• typecheck – checks TypeScript types
• lint – runs ESLint
• prettier:check – checks files with Prettier
• vitest – runs vitest tests
• vitest:watch – starts vitest watch
• test – runs vitest, prettier:check, lint and typecheck scripts

• storybook – starts storybook dev server
• storybook:build – build production storybook bundle to storybook-static
• prettier:write – formats all files with Prettier