Vulnerability Database · npm · Package report

@thi.ng/rasterize: vulnerability history, versions and safety

@thi.ng/rasterize is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm 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.

Vulert verdict on @thi.ng/rasterize 1.0.200 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 1.0.200 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 3,832 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, 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 @thi.ng/rasterize, 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
1.0.200 01 Sep 2026 none Apache-2.0 — Details →
1.0.199 25 Aug 2026 none Apache-2.0 — Details →
1.0.198 21 Jul 2026 none Apache-2.0 — Details →
1.0.197 02 Jul 2026 none Apache-2.0 — Details →
1.0.196 05 Jun 2026 none Apache-2.0 — Details →
1.0.195 23 May 2026 none Apache-2.0 — Details →
1.0.194 20 May 2026 none Apache-2.0 — Details →
1.0.192 11 May 2026 none Apache-2.0 — Details →
1.0.191 08 May 2026 none Apache-2.0 — Details →
1.0.189 26 Apr 2026 none Apache-2.0 — Details →
1.0.188 18 Apr 2026 none Apache-2.0 — Details →
1.0.187 09 Apr 2026 none Apache-2.0 — Details →
1.0.186 02 Apr 2026 none Apache-2.0 — Details →
1.0.185 21 Mar 2026 none Apache-2.0 — Details →
1.0.184 19 Mar 2026 none Apache-2.0 — Details →
1.0.183 11 Mar 2026 none Apache-2.0 — Details →
1.0.182 11 Mar 2026 none Apache-2.0 — Details →
1.0.181 08 Mar 2026 none Apache-2.0 — Details →
1.0.180 07 Mar 2026 none Apache-2.0 — Details →
1.0.179 07 Mar 2026 none Apache-2.0 — Details →
1.0.177 07 Feb 2026 none Apache-2.0 — Details →
1.0.176 23 Jan 2026 none Apache-2.0 — Details →
1.0.175 16 Jan 2026 none Apache-2.0 — Details →
1.0.174 25 Dec 2025 none Apache-2.0 — Details →
1.0.173 11 Dec 2025 none Apache-2.0 — Details →
1.0.172 03 Dec 2025 none Apache-2.0 — Details →
1.0.171 25 Nov 2025 none Apache-2.0 — Details →
1.0.170 21 Nov 2025 none Apache-2.0 — Details →
1.0.169 13 Nov 2025 none Apache-2.0 — Details →
1.0.168 25 Oct 2025 none Apache-2.0 — Details →
1.0.167 24 Oct 2025 none Apache-2.0 — Details →
1.0.163 25 Sep 2025 none Apache-2.0 — Details →
1.0.162 01 Sep 2025 none Apache-2.0 — Details →
1.0.161 11 Aug 2025 none Apache-2.0 — Details →
1.0.160 07 Aug 2025 none Apache-2.0 — Details →
1.0.159 04 Aug 2025 none Apache-2.0 — Details →
1.0.157 30 Jul 2025 none Apache-2.0 — Details →
1.0.156 21 Jul 2025 none Apache-2.0 — Details →
1.0.155 20 Jul 2025 none Apache-2.0 — Details →
1.0.154 15 Jul 2025 none Apache-2.0 — Details →
1.0.153 14 Jul 2025 none Apache-2.0 — Details →
1.0.152 13 Jul 2025 none Apache-2.0 — Details →
1.0.151 10 Jul 2025 none Apache-2.0 — Details →
1.0.150 09 Jul 2025 none Apache-2.0 — Details →
1.0.149 24 Jun 2025 none Apache-2.0 — Details →
1.0.148 18 Jun 2025 none Apache-2.0 — Details →
1.0.147 14 Jun 2025 none Apache-2.0 — Details →
1.0.146 09 Jun 2025 none Apache-2.0 — Details →
1.0.145 28 May 2025 none Apache-2.0 — Details →
1.0.144 30 Apr 2025 none Apache-2.0 — Details →
1.0.143 16 Apr 2025 none Apache-2.0 — Details →
1.0.142 01 Apr 2025 none Apache-2.0 — Details →
1.0.141 18 Mar 2025 none Apache-2.0 — Details →
1.0.140 17 Mar 2025 none Apache-2.0 — Details →
1.0.139 09 Mar 2025 none Apache-2.0 — Details →
1.0.138 25 Feb 2025 none Apache-2.0 — Details →
1.0.137 21 Feb 2025 none Apache-2.0 — Details →
1.0.136 19 Feb 2025 none Apache-2.0 — Details →
1.0.135 13 Feb 2025 none Apache-2.0 — Details →
1.0.134 29 Jan 2025 none Apache-2.0 — Details →
1.0.133 23 Jan 2025 none Apache-2.0 — Details →
1.0.132 21 Jan 2025 none Apache-2.0 — Details →
1.0.131 21 Jan 2025 none Apache-2.0 — Details →
1.0.130 17 Jan 2025 none Apache-2.0 — Details →
1.0.129 14 Jan 2025 none Apache-2.0 — Details →
1.0.128 04 Jan 2025 none Apache-2.0 — Details →
1.0.127 27 Dec 2024 none Apache-2.0 — Details →
1.0.126 12 Dec 2024 none Apache-2.0 — Details →
1.0.125 24 Nov 2024 none Apache-2.0 — Details →
1.0.124 10 Nov 2024 none Apache-2.0 — Details →
1.0.123 09 Nov 2024 none Apache-2.0 — Details →
1.0.122 03 Nov 2024 none Apache-2.0 — Details →
1.0.121 31 Oct 2024 none Apache-2.0 — Details →
1.0.120 17 Oct 2024 none Apache-2.0 — Details →
1.0.119 07 Oct 2024 none Apache-2.0 — Details →
1.0.118 05 Oct 2024 none Apache-2.0 — Details →
1.0.117 19 Sep 2024 none Apache-2.0 — Details →
1.0.116 16 Sep 2024 none Apache-2.0 — Details →
1.0.115 05 Sep 2024 none Apache-2.0 — Details →
1.0.114 28 Aug 2024 none Apache-2.0 — Details →
1.0.113 19 Aug 2024 none Apache-2.0 — Details →
1.0.112 18 Aug 2024 none Apache-2.0 — Details →
1.0.111 13 Aug 2024 none Apache-2.0 — Details →
1.0.110 10 Aug 2024 none Apache-2.0 — Details →
1.0.109 22 Jul 2024 none Apache-2.0 — Details →
1.0.108 22 Jul 2024 none Apache-2.0 — Details →
1.0.107 19 Jul 2024 none Apache-2.0 — Details →
1.0.106 16 Jul 2024 none Apache-2.0 — Details →
1.0.105 06 Jul 2024 none Apache-2.0 — Details →
1.0.104 29 Jun 2024 none Apache-2.0 — Details →
1.0.103 21 Jun 2024 none Apache-2.0 — Details →
1.0.102 08 May 2024 none Apache-2.0 — Details →
1.0.101 25 Apr 2024 none Apache-2.0 — Details →
1.0.100 23 Apr 2024 none Apache-2.0 — Details →
1.0.99 20 Apr 2024 none Apache-2.0 — Details →
1.0.98 11 Apr 2024 none Apache-2.0 — Details →
1.0.97 08 Apr 2024 none Apache-2.0 — Details →
1.0.96 29 Mar 2024 none Apache-2.0 — Details →
1.0.95 28 Mar 2024 none Apache-2.0 — Details →
1.0.94 27 Mar 2024 none Apache-2.0 — Details →
1.0.93 22 Mar 2024 none — — Details →
1.0.92 21 Mar 2024 none — — Details →
1.0.91 18 Mar 2024 none — — Details →
1.0.90 17 Mar 2024 none — — Details →
1.0.89 13 Mar 2024 none — — Details →
1.0.88 09 Mar 2024 none — — Details →
1.0.87 07 Mar 2024 none — — Details →
1.0.86 02 Mar 2024 none — — Details →
1.0.85 01 Mar 2024 none — — Details →
1.0.84 28 Feb 2024 none — — Details →
1.0.83 25 Feb 2024 none — — Details →
1.0.82 22 Feb 2024 none — — Details →
1.0.81 22 Feb 2024 none — — Details →
1.0.80 19 Feb 2024 none — — Details →
1.0.78 16 Feb 2024 none — — Details →
1.0.77 10 Feb 2024 none — — Details →
1.0.76 06 Feb 2024 none — — Details →
1.0.75 30 Jan 2024 none — — Details →
1.0.74 30 Jan 2024 none — — Details →
1.0.73 29 Jan 2024 none — — Details →

The newest 120 of 213 versions Vulert tracks. 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 @thi.ng/rasterize

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 @thi.ng/rasterize

Is @thi.ng/rasterize safe to use?

Vulert has no vulnerabilities on record for @thi.ng/rasterize in npm 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 @thi.ng/rasterize's Vulert package health score?

Vulert scores @thi.ng/rasterize 80/100, which reads as in good shape. 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 @thi.ng/rasterize affected?

No. 1.0.200, 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.

Which version of @thi.ng/rasterize should I use?

1.0.200 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @thi.ng/rasterize have?

0 vulnerabilities are recorded for @thi.ng/rasterize in the npm 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 @thi.ng/rasterize vulnerabilities disclosed?

0 vulnerabilities were recorded for @thi.ng/rasterize 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 @thi.ng/rasterize 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 @thi.ng/rasterize for upcoming vulnerabilities?

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