Everything goes through the public repository.

Before you write

Two categories of question are usually answered faster by reading than by asking. If a business is missing, has the wrong address, or has no phone number, that is almost always the state of the underlying open data rather than a fault in LeadForge — Working with open business data explains why coverage varies and where a correction should actually be made. If a search returns nothing, a larger radius or a different category is usually the cause; How LeadForge works covers the search parameters in detail.

It is also worth searching existing issues in the repository before opening a new one — the answer may already be there.

Bug reports

Open an issue at the issue tracker for anything that behaves incorrectly: a search that fails, an export that produces malformed output, a map that does not render, an import that drops rows, a layout that breaks on your screen size.

A report is far more useful when it includes:

• the exact search parameters — country, city, categories, radius, result limit — needed to reproduce it;
• what you expected to happen, and what happened instead;
• your browser and operating system;
• any message the application displayed, quoted exactly;
• a screenshot where the problem is visual — with any private information removed.

Please do not paste exported lead files into an issue. A couple of anonymised example rows is enough to show a formatting problem.

Feature requests

Feature ideas belong in the same issue tracker. The most useful requests describe the problem you are trying to solve rather than only the control you would like added — the underlying need often has a better solution than the one that first comes to mind, and it helps to know whether an export column, a filter or a whole new workflow is what would genuinely help.

Requests that would turn LeadForge into a bulk-extraction or mass-mailing tool are out of scope, and requests to add proprietary or purchased contact databases are too: the project is deliberately limited to public data sources. Because it is MIT licensed, you are free to fork it and take it in a different direction.

Data and listing concerns

If your business appears with details you want changed, the place to fix it is usually the source rather than LeadForge. Business names, addresses, phone numbers and opening hours shown in results come from OpenStreetMap, and an edit there propagates to every application built on that data, including this one. Every result card links to the underlying OpenStreetMap record so you can go straight to it.

E-mail addresses and social links found through contact discovery are read from the business’s own public website at the moment you request it; LeadForge stores nothing about them, so removing or changing them on that website is what takes effect. Nothing you or anyone else looks up is kept on a LeadForge server — saved lists exist only in the browser of the person who saved them, as described in the privacy policy.

If you believe the application is presenting public data in a way that is misleading or inappropriate, open an issue describing the concern and we will look at it.

Security reports

Do not open a public issue for a suspected vulnerability. Use GitHub’s Report a vulnerability form in the Security tab of the repository, which keeps the report private between you and the maintainers.

Include the affected route or component, reproduction steps, impact, and any suggested mitigation. Reports are acknowledged as soon as practical. Please allow time for investigation and a coordinated fix before disclosing publicly. The full policy is in SECURITY.md.

Contributing

Pull requests are welcome. The repository documents how to run the project locally and which checks — linting, type checking, tests and a production build — run in continuous integration for every push and pull request. Opening an issue first is a good idea for anything larger than a fix, so the approach can be agreed before you spend time on it.

What we cannot help with

We cannot advise whether your intended outreach is lawful in your jurisdiction, write or review marketing copy, supply contact data beyond what the public sources return, or restore a saved list that was cleared from your browser — that data never leaves your device, so no copy of it exists anywhere else.