VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pm-controls: vulnerability history, versions and safety

pm-controls is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 pm-controls vulnerabilities

Vulert verdict on pm-controls 1.1.7 i

Updated on 23 Oct 2026

Careful: 1.1.7 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 58/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.1.7 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Last release 104 months ago i
  • Licence ISC 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 pm-controls, 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.1.7 09 Feb 2018 C1 ISC No Details →
1.1.6 09 Feb 2018 C1 ISC No Details →
1.1.5 09 Feb 2018 C1 ISC No Details →
1.1.4 09 Feb 2018 C1 ISC No Details →
1.1.3 09 Feb 2018 C1 ISC No Details →
1.1.2 09 Feb 2018 C1 ISC No Details →
1.1.1 07 Feb 2018 C1 ISC No Details →
1.1.0 05 Feb 2018 C1 ISC No Details →
1.0.22 02 Feb 2018 C1 ISC No Details →
1.0.21 02 Feb 2018 C1 ISC No Details →
1.0.20 02 Feb 2018 C1 ISC No Details →
1.0.19 02 Feb 2018 C1 ISC No Details →
1.0.18 31 Jan 2018 C1 ISC No Details →
1.0.17 31 Jan 2018 C1 ISC No Details →
1.0.16 31 Jan 2018 C1 ISC No Details →
1.0.15 30 Jan 2018 C1 ISC No Details →
1.0.14 30 Jan 2018 C1 ISC No Details →
1.0.13 30 Jan 2018 C1 ISC No Details →
1.0.12 30 Jan 2018 C1 ISC No Details →
1.0.11 30 Jan 2018 C1 ISC No Details →
1.0.10 30 Jan 2018 C1 ISC No Details →
1.0.9 29 Jan 2018 C1 ISC No Details →
1.0.8 29 Jan 2018 C1 ISC No Details →
1.0.7 29 Jan 2018 C1 ISC No Details →
1.0.6 26 Jan 2018 C1 ISC No Details →
1.0.5 26 Jan 2018 C1 ISC No Details →
1.0.4 26 Jan 2018 C1 ISC No Details →
1.0.3 25 Jan 2018 C1 ISC No Details →
1.0.2 25 Jan 2018 C1 ISC No Details →
1.0.1 24 Jan 2018 C1 ISC No Details →
1.0.0 23 Jan 2018 C1 ISC No Details →
0.0.132 22 Jan 2018 C1 ISC No Details →
0.0.131 22 Jan 2018 C1 ISC No Details →
0.0.130 22 Jan 2018 C1 ISC No Details →
0.0.129 21 Jan 2018 C1 ISC No Details →
0.0.128 21 Jan 2018 C1 ISC No Details →
0.0.127 21 Jan 2018 C1 ISC No Details →
0.0.126 21 Jan 2018 C1 ISC No Details →
0.0.125 21 Jan 2018 C1 ISC No Details →
0.0.124 19 Jan 2018 C1 ISC No Details →
0.0.123 19 Jan 2018 C1 ISC No Details →
0.0.122 19 Jan 2018 C1 ISC No Details →
0.0.121 19 Jan 2018 C1 ISC No Details →
0.0.120 18 Jan 2018 C1 ISC No Details →
0.0.119 18 Jan 2018 C1 ISC No Details →
0.0.117 18 Jan 2018 C1 ISC No Details →
0.0.116 18 Jan 2018 C1 ISC No Details →
0.0.115 18 Jan 2018 C1 ISC No Details →
0.0.114 17 Jan 2018 C1 ISC No Details →
0.0.113 17 Jan 2018 C1 ISC No Details →
0.0.112 17 Jan 2018 C1 ISC No Details →
0.0.111 16 Jan 2018 C1 ISC No Details →
0.0.109 16 Jan 2018 C1 ISC No Details →
0.0.108 15 Jan 2018 C1 ISC No Details →
0.0.107 15 Jan 2018 C1 ISC No Details →
0.0.106 12 Jan 2018 C1 ISC No Details →
0.0.105 12 Jan 2018 C1 ISC No Details →
0.0.104 12 Jan 2018 C1 ISC No Details →
0.0.103 11 Jan 2018 C1 ISC No Details →
0.0.102 11 Jan 2018 C1 ISC No Details →
0.0.101 11 Jan 2018 C1 ISC No Details →
0.0.100 10 Jan 2018 C1 ISC No Details →
0.0.99 10 Jan 2018 C1 ISC No Details →
0.0.98 09 Jan 2018 C1 ISC No Details →
0.0.96 05 Jan 2018 C1 ISC No Details →
0.0.95 04 Jan 2018 C1 ISC No Details →
0.0.94 04 Jan 2018 C1 ISC No Details →
0.0.93 04 Jan 2018 C1 ISC No Details →
0.0.92 02 Jan 2018 C1 ISC No Details →
0.0.91 19 Dec 2017 C1 ISC No Details →
0.0.90 19 Dec 2017 C1 ISC No Details →
0.0.89 12 Dec 2017 C1 ISC No Details →
0.0.88 12 Dec 2017 C1 ISC No Details →
0.0.87 07 Dec 2017 C1 ISC No Details →
0.0.86 07 Dec 2017 C1 ISC No Details →
0.0.85 05 Dec 2017 C1 ISC No Details →
0.0.84 05 Dec 2017 C1 ISC No Details →
0.0.83 04 Dec 2017 C1 ISC No Details →
0.0.82 04 Dec 2017 C1 ISC No Details →
0.0.81 01 Dec 2017 C1 ISC No Details →
0.0.80 30 Nov 2017 C1 ISC No Details →
0.0.79 30 Nov 2017 C1 ISC No Details →
0.0.78 29 Nov 2017 C1 ISC No Details →
0.0.77 29 Nov 2017 C1 ISC No Details →
0.0.76 29 Nov 2017 C1 ISC No Details →
0.0.75 17 Nov 2017 C1 ISC No Details →
0.0.74 17 Nov 2017 C1 ISC No Details →
0.0.73 16 Nov 2017 C1 ISC No Details →
0.0.72 16 Nov 2017 C1 ISC No Details →
0.0.71 16 Nov 2017 C1 ISC No Details →
0.0.70 16 Nov 2017 C1 ISC No Details →
0.0.69 16 Nov 2017 C1 ISC No Details →
0.0.68 13 Nov 2017 C1 ISC No Details →
0.0.67 06 Nov 2017 C1 ISC No Details →
0.0.66 06 Nov 2017 C1 ISC No Details →
0.0.65 06 Nov 2017 C1 ISC No Details →
0.0.64 01 Nov 2017 C1 ISC No Details →
0.0.63 27 Oct 2017 C1 ISC No Details →
0.0.62 24 Oct 2017 C1 ISC No Details →
0.0.61 23 Oct 2017 C1 ISC No Details →
0.0.60 20 Oct 2017 C1 — No Details →
0.0.59 16 Oct 2017 C1 — No Details →
0.0.58 13 Oct 2017 C1 — No Details →
0.0.57 13 Oct 2017 C1 — No Details →
0.0.56 12 Oct 2017 C1 — No Details →
0.0.55 11 Oct 2017 C1 — No Details →
0.0.54 11 Oct 2017 C1 — No Details →
0.0.53 10 Oct 2017 C1 — No Details →
0.0.52 09 Oct 2017 C1 — No Details →
0.0.51 06 Oct 2017 C1 — No Details →
0.0.50 06 Oct 2017 C1 — No Details →
0.0.49 06 Oct 2017 C1 — No Details →
0.0.48 06 Oct 2017 C1 — No Details →
0.0.47 06 Oct 2017 C1 — No Details →
0.0.46 05 Oct 2017 C1 — No Details →
0.0.45 05 Oct 2017 C1 — No Details →
0.0.44 05 Oct 2017 C1 — No Details →
0.0.43 05 Oct 2017 C1 — No Details →
0.0.42 04 Oct 2017 C1 — No Details →
0.0.41 03 Oct 2017 C1 — No Details →

The newest 120 of 158 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pm-controls

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious Package in pm-controls N/A critical No fix published 03 Sep 2020

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 pm-controls

Is pm-controls safe to use?

Vulert records 1 vulnerabilities for pm-controls in npm: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is pm-controls's Vulert package health score?

Vulert scores pm-controls 58/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of pm-controls affected?

Yes. 1.1.7, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of pm-controls should I use?

1.1.7 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 pm-controls have?

1 vulnerability is recorded for pm-controls in the npm ecosystem: 1 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 pm-controls vulnerabilities disclosed?

0 vulnerabilities were recorded for pm-controls in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 pm-controls 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 pm-controls for upcoming vulnerabilities?

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