VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/nishanths/predeclared: vulnerability history, versions and safety

github.com/nishanths/predeclared 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/nishanths/predeclared vulnerabilities

Vulert verdict on github.com/nishanths/predeclared v0.3.1 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.3.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 30 i
  • OpenSSF scorecard 1/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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/nishanths/predeclared, 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.3.1 11 Oct 2026 none BSD-3-Clause — Details →
v0.3.1-0.20261010181750-496b0e18fbcd 10 Oct 2026 none BSD-3-Clause — Details →
v0.3.1-0.20260930155747-1a4257faacef 30 Sep 2026 none BSD-3-Clause — Details →
v0.2.3-0.20260926201519-ea8d639aff5d 26 Sep 2026 none BSD-3-Clause — Details →
v0.3.0 26 Sep 2026 none BSD-3-Clause — Details →
v0.2.3-0.20250331095553-51e8c974458a 31 Mar 2025 none BSD-3-Clause — Details →
v0.2.3-0.20241205035748-95afbbb1c0f1 05 Dec 2024 none BSD-3-Clause — Details →
v0.2.3-0.20241018171858-245576f9a85c 18 Oct 2024 none BSD-3-Clause — Details →
v0.2.3-0.20230427235952-31fd237ab753 27 Apr 2023 none BSD-3-Clause — Details →
v0.2.3-0.20220909164353-5f2f810c9ae6 09 Sep 2022 none BSD-3-Clause — Details →
v0.2.2 04 Apr 2022 none BSD-3-Clause — Details →
v0.2.2-0.20220404185314-cad15dcac882 04 Apr 2022 none BSD-3-Clause — Details →
v0.2.1 02 Jan 2021 none BSD-3-Clause — Details →
v0.2.0 02 Jan 2021 none BSD-3-Clause — Details →
v0.1.1 02 Jan 2021 none BSD-3-Clause — Details →
v0.1.0 01 Jan 2021 none BSD-3-Clause — Details →
v0.0.0-20200524104333-86fad755b4d3 24 May 2020 none BSD-3-Clause — Details →
v0.0.0-20200524090735-e82bfa2807b8 24 May 2020 none BSD-3-Clause — Details →
v0.0.0-20200524085651-8ee79f4a9a70 24 May 2020 none BSD-3-Clause — Details →
v0.0.0-20190419143655-18a43bb90ffc 19 Apr 2019 none BSD-3-Clause — Details →
v0.0.0-20180101024712-1f939f4d436d 01 Jan 2018 none BSD-3-Clause — Details →
v0.0.0-20171211073405-ead384016967 11 Dec 2017 none BSD-3-Clause — Details →

All 22 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/nishanths/predeclared

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/nishanths/predeclared

Is github.com/nishanths/predeclared safe to use?

Vulert has no vulnerabilities on record for github.com/nishanths/predeclared 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/nishanths/predeclared's Vulert package health score?

Vulert scores github.com/nishanths/predeclared 63/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/nishanths/predeclared affected?

No. v0.3.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 github.com/nishanths/predeclared should I use?

v0.3.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 github.com/nishanths/predeclared have?

0 vulnerabilities are recorded for github.com/nishanths/predeclared 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/nishanths/predeclared vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/nishanths/predeclared 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/nishanths/predeclared 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/nishanths/predeclared for upcoming vulnerabilities?

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