VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/packer-community/winrmcp: vulnerability history, versions and safety

github.com/packer-community/winrmcp is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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 github.com/packer-community/winrmcp vulnerabilities

Vulert verdict on github.com/packer-community/winrmcp v0.0.0-20221126162354-6e900dd2c68f i

Updated on 23 Oct 2026

Good news: v0.0.0-20221126162354-6e900dd2c68f, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20221126162354-6e900dd2c68f — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 59 i
  • OpenSSF scorecard 2/10 i
  • Last release 46 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/packer-community/winrmcp, 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
v0.0.0-20221126162354-6e900dd2c68f 26 Nov 2022 none MIT — Details →
v0.0.0-20180921211025-c76d91c1e7db 21 Sep 2018 none MIT — Details →
v0.0.0-20180921204643-0fd363d6159a 21 Sep 2018 none MIT — Details →
v0.0.0-20180102160824-81144009af58 02 Jan 2018 none MIT — Details →
v0.0.0-20180102114145-a526d1ae99fa 02 Jan 2018 none MIT — Details →
v0.0.0-20170929215132-e1b7d6e6b1b1 29 Sep 2017 none MIT — Details →
v0.0.0-20170929212901-d066271885e2 29 Sep 2017 none MIT — Details →
v0.0.0-20170821174040-21b77f4eadb9 21 Aug 2017 none MIT — Details →
v0.0.0-20170820173451-bc06e6ed63ce 20 Aug 2017 none MIT — Details →
v0.0.0-20170811185550-7f5a32419238 11 Aug 2017 none MIT — Details →
v0.0.0-20170607142156-078cc0a785c9 07 Jun 2017 none MIT — Details →
v0.0.0-20170607141540-5e31f2398c1c 07 Jun 2017 none MIT — Details →
v0.0.0-20170524223239-0861fff2f96e 24 May 2017 none MIT — Details →
v0.0.0-20170128143328-c804d432b8b7 28 Jan 2017 none MIT — Details →
v0.0.0-20170128033249-54bde545d617 28 Jan 2017 none MIT — Details →
v0.0.0-20170117094235-eda77c146d05 17 Jan 2017 none MIT — Details →
v0.0.0-20170117074213-f8312674cf8a 17 Jan 2017 none MIT — Details →
v0.0.0-20170115142732-0ee09f61ed8d 15 Jan 2017 none MIT — Details →
v0.0.0-20170115101939-68aac1d089fc 15 Jan 2017 none MIT — Details →
v0.0.0-20170114164232-d8fab3447289 14 Jan 2017 none MIT — Details →
v0.0.0-20170114120552-fd76b2836f96 14 Jan 2017 none MIT — Details →
v0.0.0-20160731162349-7f50d16167d3 31 Jul 2016 none MIT — Details →
v0.0.0-20160731153435-4d66a2b4df98 31 Jul 2016 none MIT — Details →
v0.0.0-20160525131443-0c3004f8a8af 25 May 2016 none MIT — Details →
v0.0.0-20160522054459-794b9f5127a8 22 May 2016 none MIT — Details →
v0.0.0-20160517155433-ba03c9cf9cea 17 May 2016 none MIT — Details →
v0.0.0-20160501155052-d0ed5bd788d2 01 May 2016 none MIT — Details →
v0.0.0-20160501154700-edcdaf386f9e 01 May 2016 none MIT — Details →
v0.0.0-20160430181501-6e7294e235ad 30 Apr 2016 none MIT — Details →
v0.0.0-20160430181110-c1aa2fe06959 30 Apr 2016 none MIT — Details →
v0.0.0-20160429020439-60c9e6bd89f2 29 Apr 2016 none MIT — Details →
v0.0.0-20160429013643-2f61e000ad38 29 Apr 2016 none MIT — Details →
v0.0.0-20160415142442-606243c91c0b 15 Apr 2016 none MIT — Details →
v0.0.0-20160310040704-f1bcf36a69fa 10 Mar 2016 none MIT — Details →
v0.0.0-20160310013248-f41628ffe879 10 Mar 2016 none MIT — Details →
v0.0.0-20151015162031-3d184cea22ee 15 Oct 2015 none MIT — Details →
v0.0.0-20151014160415-2beb215270b7 14 Oct 2015 none MIT — Details →
v0.0.0-20150524214855-743b1afe5ee3 24 May 2015 none MIT — Details →
v0.0.0-20150524214837-c5425e17979d 24 May 2015 none MIT — Details →
v0.0.0-20150331020813-650a91d1da6d 31 Mar 2015 none MIT — Details →
v0.0.0-20150331020347-2c6c6803e192 31 Mar 2015 none MIT — Details →
v0.0.0-20150308025444-647b40e50fc8 08 Mar 2015 none MIT — Details →
v0.0.0-20150126164916-27f05e6c6ce5 26 Jan 2015 none MIT — Details →
v0.0.0-20150125164033-19ec1ad8f2c6 25 Jan 2015 none MIT — Details →
v0.0.0-20150125145350-914b4d42eca7 25 Jan 2015 none MIT — Details →
v0.0.0-20150124235517-844b03c0e914 24 Jan 2015 none MIT — Details →
v0.0.0-20150124225624-127f36d3a82d 24 Jan 2015 none MIT — Details →
v0.0.0-20150120174539-79a4fe6eccd6 20 Jan 2015 none MIT — Details →
v0.0.0-20150112154100-abdbaa7e52de 12 Jan 2015 none MIT — Details →
v0.0.0-20150111225323-6181482320f0 11 Jan 2015 none MIT — Details →
v0.0.0-20150111001841-294dd8154d94 11 Jan 2015 none MIT — Details →
v0.0.0-20150110232700-81909505380d 10 Jan 2015 none MIT — Details →
v0.0.0-20150106182422-8907e3f580b5 06 Jan 2015 none MIT — Details →
v0.0.0-20150105150549-10aff8bad6fc 05 Jan 2015 none MIT — Details →
v0.0.0-20150103182801-f303cba628cb 03 Jan 2015 none MIT — Details →
v0.0.0-20150102052453-b41d7cc4f427 02 Jan 2015 none MIT — Details →
v0.0.0-20150102045504-bbb5008d33f8 02 Jan 2015 none — — Details →
v0.0.0-20141230163048-505edb0fc697 30 Dec 2014 none — — Details →

All 58 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 github.com/packer-community/winrmcp

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 github.com/packer-community/winrmcp

Is github.com/packer-community/winrmcp safe to use?

Vulert has no vulnerabilities on record for github.com/packer-community/winrmcp in Go 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 github.com/packer-community/winrmcp's Vulert package health score?

Vulert scores github.com/packer-community/winrmcp 57/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).

Is the latest version of github.com/packer-community/winrmcp affected?

No. v0.0.0-20221126162354-6e900dd2c68f, 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 github.com/packer-community/winrmcp should I use?

v0.0.0-20221126162354-6e900dd2c68f 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 github.com/packer-community/winrmcp have?

0 vulnerabilities are recorded for github.com/packer-community/winrmcp in the Go 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 github.com/packer-community/winrmcp vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/packer-community/winrmcp 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 github.com/packer-community/winrmcp 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 github.com/packer-community/winrmcp for upcoming vulnerabilities?

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