VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pbf: vulnerability history, versions and safety

pbf 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 pbf vulnerabilities

Vulert verdict on pbf 5.1.2 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 5.1.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,170 packages i
  • Stars 884 i
  • OpenSSF scorecard 6/10 i
  • Last release 3 months ago i
  • Licence BSD-3-Clause 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 pbf, 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
5.1.2 09 Jul 2026 none BSD-3-Clause — Details →
5.1.1 08 Jul 2026 none BSD-3-Clause — Details →
5.1.0 29 May 2026 none BSD-3-Clause — Details →
5.0.0 26 May 2026 none BSD-3-Clause — Details →
4.0.2 22 May 2026 none BSD-3-Clause — Details →
4.0.1 08 Jul 2024 none BSD-3-Clause — Details →
4.0.0 08 Jul 2024 none BSD-3-Clause — Details →
3.3.0 03 Jul 2024 none BSD-3-Clause — Details →
3.2.1 11 Oct 2019 none BSD-3-Clause — Details →
3.2.0 11 Mar 2019 none BSD-3-Clause — Details →
3.1.0 27 Sep 2017 none BSD-3-Clause — Details →
3.0.5 30 Nov 2016 none BSD-3-Clause — Details →
3.0.4 14 Nov 2016 none BSD-3-Clause — Details →
3.0.3 14 Nov 2016 none BSD-3-Clause — Details →
3.0.2 30 Sep 2016 none BSD-3-Clause — Details →
3.0.1 20 Sep 2016 none BSD-3-Clause — Details →
3.0.0 30 Aug 2016 none BSD-3-Clause — Details →
2.0.1 28 May 2016 none BSD-3-Clause — Details →
1.3.7 28 May 2016 none BSD-3-Clause — Details →
2.0.0 27 May 2016 none BSD-3-Clause — Details →
1.3.6 27 May 2016 none BSD-3-Clause — Details →
1.3.5 05 Oct 2015 none non-standard — Details →
1.3.4 31 Jul 2015 none non-standard — Details →
1.3.3 31 Jul 2015 none non-standard — Details →
1.3.2 05 Mar 2015 none non-standard — Details →
1.3.1 20 Feb 2015 none non-standard — Details →
1.3.0 06 Feb 2015 none non-standard — Details →
1.2.0 05 Jan 2015 none non-standard — Details →
1.1.4 02 Jan 2015 none non-standard — Details →
1.1.3 26 Dec 2014 none non-standard — Details →
1.1.2 26 Dec 2014 none non-standard — Details →
1.1.1 26 Dec 2014 none non-standard — Details →
1.1.0 26 Dec 2014 none non-standard — Details →
1.0.0 25 Dec 2014 none non-standard — Details →
0.0.2 01 Aug 2014 none non-standard — Details →
0.0.1 10 Feb 2014 none non-standard — Details →
0.0.0 14 Jan 2014 none non-standard — Details →

All 37 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 pbf

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 pbf

Is pbf safe to use?

Vulert has no vulnerabilities on record for pbf 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 pbf's Vulert package health score?

Vulert scores pbf 87/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 pbf affected?

No. 5.1.2, 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 pbf should I use?

5.1.2 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 pbf have?

0 vulnerabilities are recorded for pbf 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 pbf vulnerabilities disclosed?

0 vulnerabilities were recorded for pbf 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 pbf 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 pbf for upcoming vulnerabilities?

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