Vulnerability Database · Go · Package report

al.essio.dev/pkg/shellescape: vulnerability history, versions and safety

al.essio.dev/pkg/shellescape 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.

Vulert verdict on al.essio.dev/pkg/shellescape v1.6.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release v1.6.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 201 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month 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 al.essio.dev/pkg/shellescape, 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
v1.6.2-0.20260902021240-693bd3506cec 02 Sep 2026 none MIT — Details →
v1.6.1 01 Sep 2026 none MIT — Details →
v1.6.1-rc1 07 Mar 2026 none MIT — Details →
v1.6.1-0.20260122223958-d45489977a7e 22 Jan 2026 none MIT — Details →
v0.0.0-20250626071713-b09271781b1a 26 Jun 2025 none MIT — Details →
v1.6.1-0.20250626071713-b09271781b1a 26 Jun 2025 none MIT — Details →
v1.6.1-0.20250411034714-0eec8e832789 11 Apr 2025 none MIT — Details →
v0.0.0-20250225181140-26fa1b3cc48d 25 Feb 2025 none MIT — Details →
v1.6.0 25 Feb 2025 none MIT — Details →
v1.5.2-0.20241112193253-853065111c4c 12 Nov 2024 none MIT — Details →
v1.5.1 08 Oct 2024 none MIT — Details →
v1.5.1-0.20241008221814-5ab9730e7dbc 08 Oct 2024 none MIT — Details →
v1.5.1-rc1 08 Oct 2024 none MIT — Details →
v1.5.1-0.20240722023733-c769a1daef4c 22 Jul 2024 none MIT — Details →
v1.5.0 22 Jul 2024 none MIT — Details →
v0.0.0-20170105083845-52074bc9df61 05 Jan 2017 none MIT — Details →

All 16 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 al.essio.dev/pkg/shellescape

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 al.essio.dev/pkg/shellescape

Is al.essio.dev/pkg/shellescape safe to use?

Vulert has no vulnerabilities on record for al.essio.dev/pkg/shellescape 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 al.essio.dev/pkg/shellescape's Vulert package health score?

Vulert scores al.essio.dev/pkg/shellescape 73/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 al.essio.dev/pkg/shellescape affected?

No. v1.6.1, 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 al.essio.dev/pkg/shellescape should I use?

v1.6.1 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 al.essio.dev/pkg/shellescape have?

0 vulnerabilities are recorded for al.essio.dev/pkg/shellescape 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 al.essio.dev/pkg/shellescape vulnerabilities disclosed?

0 vulnerabilities were recorded for al.essio.dev/pkg/shellescape 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 al.essio.dev/pkg/shellescape 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 al.essio.dev/pkg/shellescape for upcoming vulnerabilities?

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