Czy Leadsclean jest bezpieczny?

Leadsclean — Nerq Wynik zaufania 42.5/100 (Ocena E). Na podstawie analizy 3 wymiarów zaufania, jest ma istotne obawy dotyczące bezpieczeństwa. Ostatnia aktualizacja: 2026-04-01.

Zachowaj ostrożność z Leadsclean. Leadsclean is a software tool with a Nerq Wynik zaufania of 42.5/100 (E), based on 3 independent data dimensions. Jest poniżej zalecanego progu wynoszącego 70. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-01. Dane odczytywalne maszynowo (JSON).

Czy Leadsclean jest bezpieczny?

NIE — UŻYWAJ Z OSTROŻNOŚCIĄ — Leadsclean has a Nerq Wynik zaufania of 42.5/100 (E). Ma poniżej przeciętne sygnały zaufania ze znaczącymi lukami w zakresie bezpieczeństwa, konserwacji lub dokumentacji. Niezalecany do użytku produkcyjnego bez dokładnego ręcznego przeglądu i dodatkowych środków bezpieczeństwa.

Analiza bezpieczeństwa → Raport prywatności {name} →

Jaki jest wynik zaufania Leadsclean?

Leadsclean has a Nerq Wynik zaufania of 42.5/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.

Konserwacja
0
Dokumentacja
0
Popularność
0

Jakie są kluczowe ustalenia bezpieczeństwa dla Leadsclean?

Leadsclean's strongest signal is konserwacja at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Maintenance: 0/100 — low maintenance activity
Documentation: 0/100 — limited documentation
Popularity: 0/100 — 1 stars on pulsemcp

Czym jest Leadsclean i kto go utrzymuje?

Autorhttps://github.com/edition/leadsclean
Kategoriamarketing
Gwiazdki1
Źródłohttps://github.com/edition/leadsclean

Popularne alternatywy w marketing

sansan0/TrendRadar
77.0/100 · B
github
srbhr/Resume-Matcher
71.3/100 · B
github
friuns2/BlackFriday-GPTs-Prompts
72.6/100 · B
github
coreyhaines31/marketingskills
72.6/100 · B
github
RayVentura/ShortGPT
72.6/100 · B
github

What Is Leadsclean?

Leadsclean is a software tool in the marketing category: Extracts structured B2B lead intelligence from company websites.. It has 1 GitHub stars. Nerq Wynik zaufania: 42/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Leadsclean's Safety

Nerq's Wynik zaufania is calculated from 13+ independent signals aggregated into five dimensions. Here is how Leadsclean performs in each:

The overall Wynik zaufania of 42.5/100 (E) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Who Should Use Leadsclean?

Leadsclean is designed for:

Risk guidance: We recommend caution with Leadsclean. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Leadsclean's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Leadsclean's dependency tree.
  3. Opinia permissions — Understand what access Leadsclean requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Leadsclean in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=LeadsClean
  6. Sprawdź license — Confirm that Leadsclean's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
  7. Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Leadsclean

When evaluating whether Leadsclean is safe, consider these category-specific risks:

Data handling

Understand how Leadsclean processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Leadsclean's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Leadsclean. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Leadsclean connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.

License and IP compliance

Verify that Leadsclean's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Leadsclean in violation of its license can expose your organization to legal liability.

Best Practices for Using Leadsclean Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Leadsclean while minimizing risk:

Conduct regular audits

Periodically review how Leadsclean is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Leadsclean and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

Grant Leadsclean only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for security advisories

Subscribe to Leadsclean's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Leadsclean is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Leadsclean?

Even promising tools aren't right for every situation. Consider avoiding Leadsclean in these scenarios:

wynik zaufania

For each scenario, evaluate whether Leadsclean 42.5/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Leadsclean Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among marketing tools, the average Wynik zaufania is 62/100. Leadsclean's score of 42.5/100 is below the category average of 62/100.

This suggests that Leadsclean trails behind many comparable marketing tools. Organizations with strict security requirements should evaluate whether higher-scoring alternatives better meet their needs.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.

Wynik zaufania History

Nerq continuously monitors Leadsclean and recalculates its Wynik zaufania as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Leadsclean's score is updated within 24 hours.

Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Leadsclean's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=LeadsClean&include=history

Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Leadsclean are strengthening or weakening over time.

Leadsclean vs Alternatives

W kategorii marketing, Leadsclean uzyskuje 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Kluczowe wnioski

Często zadawane pytania

Czy Leadsclean jest bezpieczny w użyciu?
Zachowaj ostrożność. LeadsClean has a Nerq Wynik zaufania of 42.5/100 (E). Najsilniejszy sygnał: konserwacja (0/100). Wynik oparty na maintenance (0/100), popularity (0/100), documentation (0/100).
Czym jest Leadsclean's trust score?
LeadsClean: 42.5/100 (E). Wynik oparty na: maintenance (0/100), popularity (0/100), documentation (0/100). Wyniki są aktualizowane wraz z pojawianiem się nowych danych. API: GET nerq.ai/v1/preflight?target=LeadsClean
Jakie są bezpieczniejsze alternatywy dla Leadsclean?
W kategorii marketing, alternatywy z wyższym wynikiem to: sansan0/TrendRadar (77/100), srbhr/Resume-Matcher (71/100), friuns2/BlackFriday-GPTs-Prompts (73/100). LeadsClean uzyskuje 42.5/100.
How often is Leadsclean's safety score updated?
Nerq continuously monitors Leadsclean and updates its trust score as new data becomes available. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 42.5/100 (E), last verified 2026-04-01. API: GET nerq.ai/v1/preflight?target=LeadsClean
Czy mogę używać Leadsclean w środowisku regulowanym?
Leadsclean has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.

We use cookies for analytics and caching. Prywatność Policy