VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

scraper: vulnerability history, versions and safety

scraper is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all scraper vulnerabilities

Vulert verdict on scraper 0.29.0 i

Updated on 23 Oct 2026

Good news: 0.29.0, the version you would install today, has no known vulnerabilities.

Package health score 93/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 0.29.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.29.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.29.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,424 i
  • Last release this month i
  • Licence ISC i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for scraper, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.29.0 21 Oct 2026 none ISC — Details →
0.27.0 11 May 2026 none ISC — Details →
0.26.0 18 Mar 2026 none ISC — Details →
0.25.0 07 Dec 2025 none ISC — Details →
0.24.0 17 Aug 2025 none ISC — Details →
0.23.1 24 Feb 2025 none ISC — Details →
0.23.0 24 Feb 2025 none ISC — Details →
0.22.0 10 Dec 2024 none ISC — Details →
0.21.0 31 Oct 2024 none ISC — Details →
0.20.0 05 Aug 2024 none ISC — Details →
0.19.1 16 Jul 2024 none ISC — Details →
0.19.0 29 Feb 2024 none ISC — Details →
0.18.1 29 Oct 2023 none ISC — Details →
0.18.0 26 Oct 2023 none ISC — Details →
0.17.1 26 Jun 2023 none ISC — Details →
0.17.0 26 Jun 2023 none ISC — Details →
0.16.0 04 Apr 2023 none ISC — Details →
0.15.0 28 Feb 2023 none ISC — Details →
0.14.0 19 Dec 2022 none ISC — Details →
0.13.0 24 Apr 2022 none ISC — Details →
0.12.0 04 May 2020 none ISC — Details →
0.11.0 30 Sep 2019 none ISC — Details →
0.10.1 07 Jul 2019 none ISC — Details →
0.10.0 08 Apr 2019 none ISC — Details →
0.9.2 22 Mar 2019 none ISC — Details →
0.9.1 18 Jan 2019 none ISC — Details →
0.9.0 03 Dec 2018 none ISC — Details →
0.8.2 02 Dec 2018 none ISC — Details →
0.8.1 31 Oct 2018 none ISC — Details →
0.8.0 30 Oct 2018 none ISC — Details →
0.7.0 18 Jun 2018 none ISC — Details →
0.6.0 18 Mar 2018 none ISC — Details →
0.5.0 14 Feb 2018 none ISC — Details →
0.4.0 18 Jul 2016 none ISC — Details →
0.3.1 05 Mar 2016 none ISC — Details →
0.3.0 04 Mar 2016 none ISC — Details →
0.2.0 04 Feb 2016 none ISC — Details →
0.1.1 29 Jan 2016 none ISC — Details →
0.1.0 17 Jan 2016 none ISC — Details →

All 39 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for scraper

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About scraper

Is scraper safe to use?

Vulert has no vulnerabilities on record for scraper in crates.io at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is scraper's Vulert package health score?

Vulert scores scraper 93/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of scraper affected?

No. 0.29.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does scraper have?

0 vulnerabilities are recorded for scraper in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new scraper vulnerabilities disclosed?

0 vulnerabilities were recorded for scraper in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of scraper are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor scraper for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the scraper version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.