VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@web/config-loader: vulnerability history, versions and safety

@web/config-loader 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.

See all @web/config-loader vulnerabilities

Vulert verdict on @web/config-loader 1.0.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 13 packages i
  • Stars 2,452 i
  • OpenSSF scorecard 4/10 i
  • Last release 3 months ago i
  • Licence MIT 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 @web/config-loader, 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.0 07 Jul 2026 none MIT — Details →
0.3.3 02 Apr 2025 none MIT — Details →
0.3.2 30 Aug 2024 none MIT — Details →
0.0.0-canary-20240219104536 19 Feb 2024 none MIT — Details →
0.0.0-canary-20240219104126 19 Feb 2024 none MIT — Details →
0.0.0-canary-20240212171943 12 Feb 2024 none MIT — Details →
0.0.0-canary-20240105101412 05 Jan 2024 none MIT — Details →
0.0.0-canary-20240105095248 05 Jan 2024 none MIT — Details →
0.0.0-canary-20240105093823 05 Jan 2024 none MIT — Details →
0.0.0-canary-20240105092607 05 Jan 2024 none MIT — Details →
0.0.0-canary-20240105091725 05 Jan 2024 none MIT — Details →
0.0.0-canary-20231122093600 22 Nov 2023 none MIT — Details →
0.3.1 13 Nov 2023 none MIT — Details →
0.3.0 01 Nov 2023 none MIT — Details →
0.2.2 19 Oct 2023 none MIT — Details →
0.2.1 23 Apr 2023 none MIT — Details →
0.2.0 21 Apr 2023 none MIT — Details →
0.0.0-canary-20230420104136 20 Apr 2023 none MIT — Details →
0.0.0-canary-20230416222938 16 Apr 2023 none MIT — Details →
0.0.0-canary-20230405181124 05 Apr 2023 none MIT — Details →
0.0.0-canary-20230404134439 04 Apr 2023 none MIT — Details →
0.0.0-canary-20230404122726 04 Apr 2023 none MIT — Details →
0.1.3 20 Dec 2020 none MIT — Details →
0.1.2 03 Sep 2020 none MIT — Details →
0.1.1 11 Aug 2020 none MIT — Details →
0.1.0 11 Aug 2020 none MIT — Details →
0.0.4 05 Aug 2020 none MIT — Details →
0.0.3 22 Jul 2020 none MIT — Details →
0.0.2 09 Jul 2020 none MIT — Details →
0.0.1 26 Jun 2020 none MIT — Details →

All 30 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 @web/config-loader

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 @web/config-loader

Is @web/config-loader safe to use?

Vulert has no vulnerabilities on record for @web/config-loader 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 @web/config-loader's Vulert package health score?

Vulert scores @web/config-loader 82/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 @web/config-loader affected?

No. 1.0.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.

Which version of @web/config-loader should I use?

1.0.0 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 @web/config-loader have?

0 vulnerabilities are recorded for @web/config-loader 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 @web/config-loader vulnerabilities disclosed?

0 vulnerabilities were recorded for @web/config-loader 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 @web/config-loader 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 @web/config-loader for upcoming vulnerabilities?

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